{"id":"CVE-2026-64232","summary":"block: recompute nr_integrity_segments in blk_insert_cloned_request","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nblock: recompute nr_integrity_segments in blk_insert_cloned_request\n\nblk_insert_cloned_request() already recomputes nr_phys_segments\nagainst the bottom queue, because \"the queue settings related to\nsegment counting may differ from the original queue.\" The exact same\nreasoning applies to integrity segments: a stacked driver's underlying\nqueue can have tighter virt_boundary_mask, seg_boundary_mask, or\nmax_segment_size than the top queue, in which case\nblk_rq_count_integrity_sg() against the bottom queue produces a\ndifferent count than the cached rq-\u003enr_integrity_segments inherited\nfrom the source request by blk_rq_prep_clone().\n\nWhen the cached count is lower than the bottom queue's actual count,\nblk_rq_map_integrity_sg() trips\n\n\tBUG_ON(segments \u003e rq-\u003enr_integrity_segments);\n\non dispatch. The same families of stacked setups that motivated the\nexisting nr_phys_segments recompute -- dm-multipath fanning out to\nnvme-rdma in particular -- can produce this.\n\nMirror the nr_phys_segments handling: when the request carries\nintegrity, recompute nr_integrity_segments against the bottom queue\nand reject the request if it exceeds the bottom queue's\nmax_integrity_segments. blk_rq_count_integrity_sg() and\nqueue_max_integrity_segments() are both already available via\n\u003clinux/blk-integrity.h\u003e, which blk-mq.c includes.\n\nThis closes a latent gap in the stacking contract and brings the\nintegrity-segment accounting in line with the existing\nphys-segment accounting.","modified":"2026-07-28T04:02:01.109756789Z","published":"2026-07-24T15:23:13.729Z","database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/64xxx/CVE-2026-64232.json"},"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/0943f81e1b3176f27dbaf6db268fc69d8a94f0ba"},{"type":"WEB","url":"https://git.kernel.org/stable/c/2c6e6a18a37b905cb584eb0dda3ae482162a81ca"},{"type":"WEB","url":"https://git.kernel.org/stable/c/42929c98d044f126508baf54a65b0f87f932fa75"},{"type":"WEB","url":"https://git.kernel.org/stable/c/53a01bcc0242590eda4c452a5bd996f62457113b"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/64xxx/CVE-2026-64232.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64232"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"76c313f658d2752e8527610677164aa7094ef7a5"},{"fixed":"53a01bcc0242590eda4c452a5bd996f62457113b"},{"fixed":"0943f81e1b3176f27dbaf6db268fc69d8a94f0ba"},{"fixed":"42929c98d044f126508baf54a65b0f87f932fa75"},{"fixed":"2c6e6a18a37b905cb584eb0dda3ae482162a81ca"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-64232.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.0"},{"fixed":"6.12.92"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.34"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.0.11"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-64232.json"}}],"schema_version":"1.7.5","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"}]}