Descrizione
In the Linux kernel, the following vulnerability has been resolved: block: recompute nr_integrity_segments in blk_insert_cloned_request blk_insert_cloned_request() already recomputes nr_phys_segments against the bottom queue, because "the queue settings related to segment counting may differ from the original queue." The exact same reasoning applies to integrity segments: a stacked driver's underlying queue can have tighter virt_boundary_mask, seg_boundary_mask, or max_segment_size than the top queue, in which case blk_rq_count_integrity_sg() against the bottom queue produces a different count than the cached rq->nr_integrity_segments inherited from the source request by blk_rq_prep_clone(). When the cached count is lower than the bottom queue's actual count, blk_rq_map_integrity_sg() trips BUG_ON(segments > rq->nr_integrity_segments); on dispatch. The same families of stacked setups that motivated the existing nr_phys_segments recompute -- dm-multipath fanning out to nvme-rdma in particular -- can produce this. Mirror the nr_phys_segments handling: when the request carries integrity, recompute nr_integrity_segments against the bottom queue and reject the request if it exceeds the bottom queue's max_integrity_segments. blk_rq_count_integrity_sg() and queue_max_integrity_segments() are both already available via <linux/blk-integrity.h>, which blk-mq.c includes. This closes a latent gap in the stacking contract and brings the integrity-segment accounting in line with the existing phys-segment accounting.
Come correggere
Priorità: Alta — pianificare la correzione entro pochi giorni. Motivazione: CVSS 9.8.
Versioni da aggiornare
- Linux Linux Kernel: vulnerabili le versioni dalla
6.12precedenti alla6.12.92→ aggiornare alla6.12.92o successiva. - Linux Linux Kernel: vulnerabili le versioni dalla
6.13precedenti alla6.18.34→ aggiornare alla6.18.34o successiva. - Linux Linux Kernel: vulnerabili le versioni dalla
6.19precedenti alla7.0.11→ aggiornare alla7.0.11o successiva. - Linux Linux Kernel: vulnerabile la versione
7.1 rc1→ installare l'ultima release supportata dal vendor. - Linux Linux Kernel: vulnerabile la versione
7.1 rc2→ installare l'ultima release supportata dal vendor. - Linux Linux Kernel: vulnerabile la versione
7.1 rc3→ installare l'ultima release supportata dal vendor.
Patch e advisory
- Patch: git.kernel.org/stable/c/0943f81e1b3176f27dbaf6db268…
- Patch: git.kernel.org/stable/c/2c6e6a18a37b905cb584eb0dda3…
- Patch: git.kernel.org/stable/c/42929c98d044f126508baf54a65…
- Patch: git.kernel.org/stable/c/53a01bcc0242590eda4c452a5bd…
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 | ≥ 6.12 < 6.12.92 | 6.12.92 |
| Linux | Linux Kernel | ≥ 6.13 < 6.18.34 | 6.18.34 |
| Linux | Linux Kernel | ≥ 6.19 < 7.0.11 | 7.0.11 |
| Linux | Linux Kernel | 7.1 rc1 | — |
| Linux | Linux Kernel | 7.1 rc2 | — |
| Linux | Linux Kernel | 7.1 rc3 | — |
Riferimenti
- Patchhttps://git.kernel.org/stable/c/0943f81e1b3176f27dbaf6db268fc69d8a94f0ba
- Patchhttps://git.kernel.org/stable/c/2c6e6a18a37b905cb584eb0dda3ae482162a81ca
- Patchhttps://git.kernel.org/stable/c/42929c98d044f126508baf54a65b0f87f932fa75
- Patchhttps://git.kernel.org/stable/c/53a01bcc0242590eda4c452a5bd996f62457113b