ALSA: usb-audio: Fix DMA buffer out-of-bounds write when fill_max is set
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Fix DMA buffer out-of-bounds write when fill_max is set When a USB audio endpoint requests full packet transfers via the fill_max descriptor flag, data_ep_set_params() promotes ep->curpacksize to ep->maxpacksize. However, maxsize is left at the original sample-rate derived value. Since u->buffer_size is allocated as maxsize * packets, the resulting DMA buffer is far too small for the requested transfer length. When the USB host controller streams up to curpacksize bytes per packet, it writes past the end of the buffer via DMA, corrupting kernel heap memory. Update maxsize to curpacksize when fill_max is set so that the allocated DMA buffer size matches the actual transfer request size. [ changed to reassign maxsize only when ep->fill_max is set -- tiwai ]
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
3.5
References 8
git.kernel.org
- stable/c/10c24e6fddf4bdff0b6b05a47a4347b38e6960e8
- stable/c/b1770f9ac35c0ffc34914d52347c65dcd5ac049b
- stable/c/6cbdd11f9b05b92f4aa29f09a66e19ed0e25e66c
- stable/c/3852974608f53e530e27c21d0c6c7d79c17b3f5a
- stable/c/f9b6c9576568169139ac151f7881474f384659fd
- stable/c/04595233e5606d452f9f47e6989fc7ae7440fd40
- stable/c/bd65b7191683bebd9923904f0558b9211b9129da
- stable/c/d0199ae1666ff9ae2d1d568d64c3430d4c47f0e5