CVE-2026-64232 (GCVE-0-2026-64232)
Vulnerability from cvelistv5 – Published: 2026-07-24 15:23 – Updated: 2026-07-27 04:59
VLAI
EPSS
VEX
Title
block: recompute nr_integrity_segments in blk_insert_cloned_request
Summary
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.
Severity
9.8 (Critical)
Assigner
References
Impacted products
2 products
| Vendor | Product | Version | |
|---|---|---|---|
| Linux | Linux |
Affected:
76c313f658d2752e8527610677164aa7094ef7a5 , < 53a01bcc0242590eda4c452a5bd996f62457113b
(git)
Affected: 76c313f658d2752e8527610677164aa7094ef7a5 , < 0943f81e1b3176f27dbaf6db268fc69d8a94f0ba (git) Affected: 76c313f658d2752e8527610677164aa7094ef7a5 , < 42929c98d044f126508baf54a65b0f87f932fa75 (git) Affected: 76c313f658d2752e8527610677164aa7094ef7a5 , < 2c6e6a18a37b905cb584eb0dda3ae482162a81ca (git) |
|
| Linux | Linux |
Affected:
6.12
Unaffected: 0 , < 6.12 (semver) Unaffected: 6.12.92 , ≤ 6.12.* (semver) Unaffected: 6.18.34 , ≤ 6.18.* (semver) Unaffected: 7.0.11 , ≤ 7.0.* (semver) Unaffected: 7.1 , ≤ * (original_commit_for_fix) |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"block/blk-mq.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "53a01bcc0242590eda4c452a5bd996f62457113b",
"status": "affected",
"version": "76c313f658d2752e8527610677164aa7094ef7a5",
"versionType": "git"
},
{
"lessThan": "0943f81e1b3176f27dbaf6db268fc69d8a94f0ba",
"status": "affected",
"version": "76c313f658d2752e8527610677164aa7094ef7a5",
"versionType": "git"
},
{
"lessThan": "42929c98d044f126508baf54a65b0f87f932fa75",
"status": "affected",
"version": "76c313f658d2752e8527610677164aa7094ef7a5",
"versionType": "git"
},
{
"lessThan": "2c6e6a18a37b905cb584eb0dda3ae482162a81ca",
"status": "affected",
"version": "76c313f658d2752e8527610677164aa7094ef7a5",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"block/blk-mq.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.12"
},
{
"lessThan": "6.12",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.92",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.34",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.0.*",
"status": "unaffected",
"version": "7.0.11",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.1",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.92",
"versionStartIncluding": "6.12",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.34",
"versionStartIncluding": "6.12",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.0.11",
"versionStartIncluding": "6.12",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.1",
"versionStartIncluding": "6.12",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "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\u0027s 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\u0027s 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\u0027s\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."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-07-27T04:59:04.371Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/53a01bcc0242590eda4c452a5bd996f62457113b"
},
{
"url": "https://git.kernel.org/stable/c/0943f81e1b3176f27dbaf6db268fc69d8a94f0ba"
},
{
"url": "https://git.kernel.org/stable/c/42929c98d044f126508baf54a65b0f87f932fa75"
},
{
"url": "https://git.kernel.org/stable/c/2c6e6a18a37b905cb584eb0dda3ae482162a81ca"
}
],
"title": "block: recompute nr_integrity_segments in blk_insert_cloned_request",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-64232",
"datePublished": "2026-07-24T15:23:13.729Z",
"dateReserved": "2026-07-19T15:36:31.771Z",
"dateUpdated": "2026-07-27T04:59:04.371Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-64232",
"date": "2026-07-26",
"epss": "0.00168",
"percentile": "0.06478"
},
"nvd": "{\"cve\":{\"id\":\"CVE-2026-64232\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-07-24T16:16:52.367\",\"lastModified\":\"2026-07-27T05:16:36.857\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"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\u0027s 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\u0027s 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\u0027s\\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.\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"block/blk-mq.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"76c313f658d2752e8527610677164aa7094ef7a5\",\"lessThan\":\"53a01bcc0242590eda4c452a5bd996f62457113b\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"76c313f658d2752e8527610677164aa7094ef7a5\",\"lessThan\":\"0943f81e1b3176f27dbaf6db268fc69d8a94f0ba\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"76c313f658d2752e8527610677164aa7094ef7a5\",\"lessThan\":\"42929c98d044f126508baf54a65b0f87f932fa75\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"76c313f658d2752e8527610677164aa7094ef7a5\",\"lessThan\":\"2c6e6a18a37b905cb584eb0dda3ae482162a81ca\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"block/blk-mq.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"6.12\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"6.12\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.12.92\",\"lessThanOrEqual\":\"6.12.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.18.34\",\"lessThanOrEqual\":\"6.18.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"7.0.11\",\"lessThanOrEqual\":\"7.0.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"7.1\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H\",\"baseScore\":9.8,\"baseSeverity\":\"CRITICAL\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":3.9,\"impactScore\":5.9}]},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/0943f81e1b3176f27dbaf6db268fc69d8a94f0ba\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/2c6e6a18a37b905cb584eb0dda3ae482162a81ca\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/42929c98d044f126508baf54a65b0f87f932fa75\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/53a01bcc0242590eda4c452a5bd996f62457113b\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
Loading…
Loading…