cbcvebase.
CVE-2026-64232
published 2026-07-24

CVE-2026-64232: In the Linux kernel, the following vulnerability has been resolved: block: recompute nr_integrity_segments in blk_insert_cloned_request…

PriorityP353critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
0.46%
37.8th percentile
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 , 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.

Affected

20 ranges
VendorProductVersion rangeFixed in
linuxlinux——
linuxlinux>= 76c313f658d2752e8527610677164aa7094ef7a5 < 53a01bcc0242590eda4c452a5bd996f62457113b53a01bcc0242590eda4c452a5bd996f62457113b
linuxlinux>= 76c313f658d2752e8527610677164aa7094ef7a5 < 0943f81e1b3176f27dbaf6db268fc69d8a94f0ba0943f81e1b3176f27dbaf6db268fc69d8a94f0ba
linuxlinux>= 76c313f658d2752e8527610677164aa7094ef7a5 < 42929c98d044f126508baf54a65b0f87f932fa7542929c98d044f126508baf54a65b0f87f932fa75
linuxlinux>= 76c313f658d2752e8527610677164aa7094ef7a5 < 2c6e6a18a37b905cb584eb0dda3ae482162a81ca2c6e6a18a37b905cb584eb0dda3ae482162a81ca
linuxlinux_kernel——
linuxlinux_kernel——
linuxlinux_kernel——
linuxlinux_kernel——
linuxlinux_kernel>= 6.12 < 6.12.926.12.92
linuxlinux_kernel>= 6.13 < 6.18.346.18.34
linuxlinux_kernel>= 6.19 < 7.0.117.0.11
ubuntulinux-aws——
ubuntulinux-azure-7.0——
ubuntulinux-gcp-7.0——
ubuntulinux-nvidia——
ubuntulinux-nvidia-7.0——
ubuntulinux-nvidia-bos——
ubuntulinux-oracle-7.0——
ubuntulinux-raspi——

CVSS provenance

nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vendor_redhat9.8CRITICAL
vendor_ubuntu9.1CRITICAL
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.