Descrizione
In the Linux kernel, the following vulnerability has been resolved: ALSA: pcmtest: handle multiple wraps in random capture fill The random capture helpers assume that the data generated for one timer tick wraps the DMA ring at most once. However, b_rw describes 200 ms of audio because the timer runs at 5 Hz, so it can be several times larger than a small ring. For 48 kHz, S16_LE, four-channel capture with a 512-frame buffer, the DMA ring is 4096 bytes while one tick generates 76800 bytes. After filling the 4096-byte tail, the existing code issues a second 72704-byte write from the ring base, writing 68608 bytes beyond the ring. Both interleaved and non-interleaved capture are affected. KASAN reports the first write into the adjacent free page as a use-after-free in the random-byte generator. The underlying defect is an out-of-bounds write from the live DMA ring, not a stale DMA allocation. Split each random write repeatedly at the interleaved ring or per-channel block boundary. Keep the hardware-pointer update exactly once after the complete logical write. The issue reproduced on three of three clean boots. With this change, the same vulnerable geometry completed six times without a sanitizer finding. Boundary, pattern-fill, no-timer, open/close, and module-reload controls also completed normally. snd-pcmtest is a test driver, and selecting random fill requires an administrator-controlled module parameter. The written values come from the kernel random generator; no privilege escalation or attacker-controlled write primitive was demonstrated.
Come correggere
Priorità: Bassa — correggere con la manutenzione ordinaria. Motivazione: EPSS 0.2% (percentile 7).
Versioni da aggiornare
- Linux Linux: versione corretta
6.12.117(o successiva). - Linux Linux: versione corretta
6.18.61(o successiva). - Linux Linux: versione corretta
7.3.2(o successiva). - Linux Linux: versione corretta
7.4-rc1(o successiva). - Linux Linux: vulnerabile la versione
6.5→ installare l'ultima release supportata dal vendor.
Mitigazioni temporanee
Da applicare solo se non è possibile aggiornare subito:
- Ridurre l'esposizione del componente vulnerabile (segmentazione, accesso solo da reti fidate) finché la patch non è applicata.
Verifica
- Individuare tutti gli asset con il prodotto interessato (inventario, scanner di vulnerabilità, CMDB).
- Confrontare la versione installata con quelle indicate sopra.
- Applicare l'aggiornamento in un ambiente di test, poi in produzione; riavviare i servizi se richiesto.
- Ripetere la scansione per confermare la correzione.
Configurazioni interessate
| Vendor | Prodotto | Versioni vulnerabili | Corretta in |
|---|---|---|---|
| Linux | Linux | — | 6.12.117 |
| Linux | Linux | — | 6.18.61 |
| Linux | Linux | — | 7.3.2 |
| Linux | Linux | — | 7.4-rc1 |
| Linux | Linux | 6.5 | — |
Riferimenti
- Riferimentohttps://git.kernel.org/stable/c/5cb07a5941b1e3dbe655110618869a81af68907e
- Riferimentohttps://git.kernel.org/stable/c/6541871e8e63e721733cd120af4d9cd22c5ef62f
- Riferimentohttps://git.kernel.org/stable/c/76319a56f069bb950d9cebbc1a291cbfa94a1c1f
- Riferimentohttps://git.kernel.org/stable/c/8f8555e03bb2596b0d521c5b95c72cbd76e7d9af