Answer in brief
CVE-2026-74498 records a Unknown severity vulnerability in ALSA: usb-audio: Fix DMA buffer out-of-bounds write when fill_max is set. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=8fdff6a319e7dac757c558bd283dc4577e68cde7 <3852974608f53e530e27c21d0c6c7d79c17b3f5a || >=8fdff6a319e7dac757c558bd283dc4577e68cde7 <f9b6c9576568169139ac151f7881474f384659fd || >=8fdff6a319e7dac757c558bd283dc4577e68cde7 <04595233e5606d452f9f47e6989fc7ae7440fd40 || >=8fdff6a319e7dac757c558bd283dc4577e68cde7 <bd65b7191683bebd9923904f0558b9211b9129da || >=8fdff6a319e7dac757c558bd283dc4577e68cde7 <d0199ae1666ff9ae2d1d568d64c3430d4c47f0e5 | 3852974608f53e530e27c21d0c6c7d79c17b3f5a, f9b6c9576568169139ac151f7881474f384659fd, 04595233e5606d452f9f47e6989fc7ae7440fd40, bd65b7191683bebd9923904f0558b9211b9129da, d0199ae1666ff9ae2d1d568d64c3430d4c47f0e5 |
| Linux/Linuxgeneric | 3.5 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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 ]
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-74498 records a Unknown severity vulnerability in ALSA: usb-audio: Fix DMA buffer out-of-bounds write when fill_max is set. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=8fdff6a319e7dac757c558bd283dc4577e68cde7 <3852974608f53e530e27c21d0c6c7d79c17b3f5a || >=8fdff6a319e7dac757c558bd283dc4577e68cde7 <f9b6c9576568169139ac151f7881474f384659fd || >=8fdff6a319e7dac757c558bd283dc4577e68cde7 <04595233e5606d452f9f47e6989fc7ae7440fd40 || >=8fdff6a319e7dac757c558bd283dc4577e68cde7 <bd65b7191683bebd9923904f0558b9211b9129da || >=8fdff6a319e7dac757c558bd283dc4577e68cde7 <d0199ae1666ff9ae2d1d568d64c3430d4c47f0e5 | 3852974608f53e530e27c21d0c6c7d79c17b3f5a, f9b6c9576568169139ac151f7881474f384659fd, 04595233e5606d452f9f47e6989fc7ae7440fd40, bd65b7191683bebd9923904f0558b9211b9129da, d0199ae1666ff9ae2d1d568d64c3430d4c47f0e5 |
| Linux/Linuxgeneric | 3.5 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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 ]
Quoted source text, attributed separately from HOL analysis.