Answer in brief
CVE-2026-64232 records a Unknown severity vulnerability in block: recompute nr_integrity_segments in blk_insert_cloned_request. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=76c313f658d2752e8527610677164aa7094ef7a5 <53a01bcc0242590eda4c452a5bd996f62457113b || >=76c313f658d2752e8527610677164aa7094ef7a5 <0943f81e1b3176f27dbaf6db268fc69d8a94f0ba || >=76c313f658d2752e8527610677164aa7094ef7a5 <42929c98d044f126508baf54a65b0f87f932fa75 || >=76c313f658d2752e8527610677164aa7094ef7a5 <2c6e6a18a37b905cb584eb0dda3ae482162a81ca | 53a01bcc0242590eda4c452a5bd996f62457113b, 0943f81e1b3176f27dbaf6db268fc69d8a94f0ba, 42929c98d044f126508baf54a65b0f87f932fa75, 2c6e6a18a37b905cb584eb0dda3ae482162a81ca |
| Linux/Linuxgeneric | 6.12 | Not reported |
Published upstream
Jul 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64232 records a Unknown severity vulnerability in block: recompute nr_integrity_segments in blk_insert_cloned_request. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=76c313f658d2752e8527610677164aa7094ef7a5 <53a01bcc0242590eda4c452a5bd996f62457113b || >=76c313f658d2752e8527610677164aa7094ef7a5 <0943f81e1b3176f27dbaf6db268fc69d8a94f0ba || >=76c313f658d2752e8527610677164aa7094ef7a5 <42929c98d044f126508baf54a65b0f87f932fa75 || >=76c313f658d2752e8527610677164aa7094ef7a5 <2c6e6a18a37b905cb584eb0dda3ae482162a81ca | 53a01bcc0242590eda4c452a5bd996f62457113b, 0943f81e1b3176f27dbaf6db268fc69d8a94f0ba, 42929c98d044f126508baf54a65b0f87f932fa75, 2c6e6a18a37b905cb584eb0dda3ae482162a81ca |
| Linux/Linuxgeneric | 6.12 | Not reported |
Published upstream
Jul 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.