Descrizione
In the Linux kernel, the following vulnerability has been resolved: udf: don't use eloc after the end of the unallocated space table When udf_next_aext() returns 0, its eloc, elen and etype outputs hold no defined value. Two walks of the unallocated space table still use eloc after the walk has reached the end of the table. udf_table_prealloc_blocks() looks for a free extent starting at first_block and decides whether it found one by comparing eloc with first_block after the walk. If the table's list ends in a continuation descriptor that leads to an empty allocation extent, eloc is then the block of that allocation extent, which is in use, and if that is first_block, the block is handed out as preallocation. Once udf_discard_prealloc() no longer frees the wrong block, this is what still makes fsx in generic/091 and generic/263 read back bad data on a table, in about one run in four. Only take the extent if the walk stopped at it. When udf_table_free_blocks() cannot merge the freed blocks into an existing extent, it appends a new one and sets only its block number, so the partition reference comes from whatever eloc held after the walk, and with long allocation descriptors it is written to disk. For a table without extents, eloc was never set. Take the partition reference from the freed blocks instead. Short allocation descriptors do not store the partition reference, which is why this half remains a latent long-descriptor fix rather than a reproduced failure.
Come correggere
Priorità: Bassa — correggere con la manutenzione ordinaria. Motivazione: EPSS 0.2% (percentile 6).
Versioni da aggiornare
- Linux Linux: versione corretta
6.12.118(o successiva). - Linux Linux: versione corretta
6.18.64(o successiva). - Linux Linux: versione corretta
7.3.5(o successiva). - Linux Linux: versione corretta
7.4-rc2(o successiva). - Linux Linux: vulnerabile la versione
2.6.12→ 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.118 |
| Linux | Linux | — | 6.18.64 |
| Linux | Linux | — | 7.3.5 |
| Linux | Linux | — | 7.4-rc2 |
| Linux | Linux | 2.6.12 | — |
Riferimenti
- Riferimentohttps://git.kernel.org/stable/c/0ceb311c0f7af4f4b38fc1066178b84a60d61a05
- Riferimentohttps://git.kernel.org/stable/c/812d49a09ce0a8fcc784349d6a95e975a4af51cf
- Riferimentohttps://git.kernel.org/stable/c/94401199df90e1c2a50c6e4b73618ac5a4ba83ba
- Riferimentohttps://git.kernel.org/stable/c/9ecd3d7ed7d7a57ee6af27dc22be0b3fdc9526f7