Descrizione
In the Linux kernel, the following vulnerability has been resolved: ext4: handle wraparound when searching for blocks for indirect mapped blocks Commit 4865c768b563 ("ext4: always allocate blocks only from groups inode can use") restricts what blocks will be allocated for indirect block based files to block numbers that fit within 32-bit block numbers. However, when using a review bot running on the latest Gemini LLM to check this commit when backporting into an LTS based kernel, it raised this concern: If ac->ac_g_ex.fe_group is >= ngroups (for instance, if the goal group was populated via stream allocation from s_mb_last_groups), then start will be >= ngroups. Does this allow allocating blocks beyond the 32-bit limit for indirect block mapped files? The commit message mentions that ext4_mb_scan_groups_linear() takes care to not select unsupported groups. However, its loop uses group = *start, and the very first iteration will call ext4_mb_scan_group() with this unsupported group because next_linear_group() is only called at the end of the iteration. After reviewing the code paths involved and considering the LLM review, I determined that this can happen when there is a file system where some files/directories are extent-mapped and others are indirect-block mapped. To address this, add a safety clamp in ext4_mb_scan_groups().
Come correggere
Priorità: Alta — pianificare la correzione entro pochi giorni. Motivazione: CVSS 9.8.
Versioni da aggiornare
- Linux Linux Kernel: vulnerabili le versioni dalla
5.15.203precedenti alla5.16→ aggiornare alla5.16o successiva. - Linux Linux Kernel: vulnerabili le versioni dalla
6.6.130precedenti alla6.6.134→ aggiornare alla6.6.134o successiva. - Linux Linux Kernel: vulnerabili le versioni dalla
6.12.77precedenti alla6.12.80→ aggiornare alla6.12.80o successiva. - Linux Linux Kernel: vulnerabili le versioni dalla
6.18.14precedenti alla6.18.21→ aggiornare alla6.18.21o successiva. - Linux Linux Kernel: vulnerabili le versioni dalla
6.19.4precedenti alla6.19.11→ aggiornare alla6.19.11o successiva. - Linux Linux Kernel: vulnerabile la versione
6.1.167→ installare l'ultima release supportata dal vendor.
Patch e advisory
- Patch: git.kernel.org/stable/c/12624c5b724a81e14e532972b40…
- Patch: git.kernel.org/stable/c/2a368ccddfc492a0aa951e2caef…
- Patch: git.kernel.org/stable/c/4bec4a498ce86314d470ae61441…
- Patch: git.kernel.org/stable/c/83170a05908b6cf2fb3235d3065…
- Patch: git.kernel.org/stable/c/bb81702370fad22c06ca12b6e16…
- Patch: git.kernel.org/stable/c/f89bba144938921a2249237ad04…
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 Kernel | ≥ 5.15.203 < 5.16 | 5.16 |
| Linux | Linux Kernel | ≥ 6.6.130 < 6.6.134 | 6.6.134 |
| Linux | Linux Kernel | ≥ 6.12.77 < 6.12.80 | 6.12.80 |
| Linux | Linux Kernel | ≥ 6.18.14 < 6.18.21 | 6.18.21 |
| Linux | Linux Kernel | ≥ 6.19.4 < 6.19.11 | 6.19.11 |
| Linux | Linux Kernel | 6.1.167 | — |
Riferimenti
- Patchhttps://git.kernel.org/stable/c/12624c5b724a81e14e532972b40d863b0de3b7d1
- Patchhttps://git.kernel.org/stable/c/2a368ccddfc492a0aa951e2caef2985f20e96503
- Patchhttps://git.kernel.org/stable/c/4bec4a498ce86314d470ae6144120461f2138c29
- Patchhttps://git.kernel.org/stable/c/83170a05908b6cf2fb3235d3065bf613ff866f3c
- Patchhttps://git.kernel.org/stable/c/bb81702370fad22c06ca12b6e1648754dbc37e0f
- Patchhttps://git.kernel.org/stable/c/f89bba144938921a2249237ad04a0183ff3f8930