CVE-2026-74498ALSA: usb-audio: Fix DMA buffer out-of-bounds write when fill_max is set
- —Not scoredno CVSS score yet
- 0.18%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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
ID reserved
By Linux
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.18% · top 93% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 8fdff6a319e7dac757c558bd283dc4577e68cde7 – < 10c24e6fddf4bdff0b6b05a47a4347b38e6960e8
- affected 8fdff6a319e7dac757c558bd283dc4577e68cde7 – < b1770f9ac35c0ffc34914d52347c65dcd5ac049b
- affected 8fdff6a319e7dac757c558bd283dc4577e68cde7 – < 6cbdd11f9b05b92f4aa29f09a66e19ed0e25e66c
- affected 8fdff6a319e7dac757c558bd283dc4577e68cde7 – < 3852974608f53e530e27c21d0c6c7d79c17b3f5a
- affected 8fdff6a319e7dac757c558bd283dc4577e68cde7 – < f9b6c9576568169139ac151f7881474f384659fd
- affected 8fdff6a319e7dac757c558bd283dc4577e68cde7 – < 04595233e5606d452f9f47e6989fc7ae7440fd40
- affected 8fdff6a319e7dac757c558bd283dc4577e68cde7 – < bd65b7191683bebd9923904f0558b9211b9129da
- affected 8fdff6a319e7dac757c558bd283dc4577e68cde7 – < d0199ae1666ff9ae2d1d568d64c3430d4c47f0e5
- affected 3.5
- unaffected < 3.5
- unaffected 5.10.265 – ≤ 5.10.*
- unaffected 5.15.216 – ≤ 5.15.*
- unaffected 6.1.183 – ≤ 6.1.*
- unaffected 6.6.151 – ≤ 6.6.*
- unaffected 6.12.103 – ≤ 6.12.*
- unaffected 6.18.44 – ≤ 6.18.*
- unaffected 7.1.8 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References8
- https://git.kernel.org/stable/c/10c24e6fddf4bdff0b6b05a47a4347b38e6960e8 (opens in a new tab)
- https://git.kernel.org/stable/c/b1770f9ac35c0ffc34914d52347c65dcd5ac049b (opens in a new tab)
- https://git.kernel.org/stable/c/6cbdd11f9b05b92f4aa29f09a66e19ed0e25e66c (opens in a new tab)
- https://git.kernel.org/stable/c/3852974608f53e530e27c21d0c6c7d79c17b3f5a (opens in a new tab)
- https://git.kernel.org/stable/c/f9b6c9576568169139ac151f7881474f384659fd (opens in a new tab)
- https://git.kernel.org/stable/c/04595233e5606d452f9f47e6989fc7ae7440fd40 (opens in a new tab)
- https://git.kernel.org/stable/c/bd65b7191683bebd9923904f0558b9211b9129da (opens in a new tab)
- https://git.kernel.org/stable/c/d0199ae1666ff9ae2d1d568d64c3430d4c47f0e5 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-59691 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-74498)Record last updated .