1. 30 Dec, 2010 1 commit
    • Dan Rosenberg's avatar
      sound: Prevent buffer overflow in OSS load_mixer_volumes · d81a12bc
      Dan Rosenberg authored
      The load_mixer_volumes() function, which can be triggered by
      unprivileged users via the SOUND_MIXER_SETLEVELS ioctl, is vulnerable to
      a buffer overflow.  Because the provided "name" argument isn't
      guaranteed to be NULL terminated at the expected 32 bytes, it's possible
      to overflow past the end of the last element in the mixer_vols array.
      Further exploitation can result in an arbitrary kernel write (via
      subsequent calls to load_mixer_volumes()) leading to privilege
      escalation, or arbitrary kernel reads via get_mixer_levels().  In
      addition, the strcmp() may leak bytes beyond the mixer_vols array.
      Signed-off-by: default avatarDan Rosenberg <drosenberg@vsecurity.com>
      Cc: stable <stable@kernel.org>
      Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      d81a12bc
  2. 23 Dec, 2010 5 commits
  3. 21 Dec, 2010 3 commits
  4. 20 Dec, 2010 1 commit
  5. 17 Dec, 2010 3 commits
  6. 15 Dec, 2010 2 commits
  7. 13 Dec, 2010 1 commit
  8. 09 Dec, 2010 5 commits
  9. 08 Dec, 2010 1 commit
    • Anssi Hannula's avatar
      ALSA: hda - Reset sample sizes and max bitrates when reading ELD · 0bbaee3a
      Anssi Hannula authored
      When a new HDMI/DP device is plugged in, hdmi_update_short_audio_desc()
      is called for every SAD (Short Audio Descriptor) in the ELD data. For
      LPCM coding type SAD defines the supported sample sizes. For several
      other coding types (such as AC-3), a maximum bitrate is defined.
      
      The maximum bitrate and sample size fields are not always cleared.
      Therefore, if a device is unplugged and a different one is plugged in,
      and the coding types of some SAD positions differ between the devices,
      the old max_bitrate or sample_bits values will persist if the new SADs
      do not define those values.
      
      The leftover max_bitrate and sample_bits do not cause any issues other
      than wrongly showing up in eld#X.Y procfs file and kernel log.
      
      Fix that by always clearing sample_bits and max_bitrate when reading
      SADs.
      Signed-off-by: default avatarAnssi Hannula <anssi.hannula@iki.fi>
      Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      0bbaee3a
  10. 07 Dec, 2010 5 commits
  11. 06 Dec, 2010 4 commits
  12. 04 Dec, 2010 1 commit
  13. 03 Dec, 2010 2 commits
  14. 02 Dec, 2010 5 commits
  15. 01 Dec, 2010 1 commit