Files
vuln-cve/data/2026/64xxx/CVE-2026-64232.json
T

226 lines
12 KiB
JSON

{
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"cveMetadata": {
"cveId": "CVE-2026-64232",
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"state": "PUBLISHED",
"assignerShortName": "Linux",
"dateReserved": "2026-07-19T15:36:31.771Z",
"datePublished": "2026-07-24T15:23:13.729Z",
"dateUpdated": "2026-10-19T20:28:16.033Z"
},
"containers": {
"cna": {
"providerMetadata": {
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux",
"dateUpdated": "2026-08-05T12:40:12.752Z"
},
"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'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->nr_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 > rq->nr_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<linux/blk-integrity.h>, 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": {
"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"
},
"scenarios": [
{
"lang": "en",
"value": "AV:N - A PI-enabled iSER or NVMe/RDMA target can expose the affected request-based dm-multipath device, allowing remote storage commands to reach the vulnerable clone-dispatch path.\nAC:L - Once the affected storage topology is configured, the attacker controls the metadata-bearing I/O requests and can trigger the segment-count mismatch repeatedly without winning an uncontrollable race.\nPR:N - Targets configured with dynamic ACLs and authentication disabled, or NVMe allow_any_host, permit unauthenticated remote initiators to issue the required I/O.\nUI:N - No victim action is required after the network storage target and affected backend are operational.\nS:U - The corruption occurs within the host kernel processing the target's block I/O and does not inherently cross a separate security authority such as a guest-host boundary.\nC:H - The undersized integrity scatterlist is populated beyond its declared bounds before the BUG_ON executes, permitting adjacent kernel-memory corruption that could be leveraged for arbitrary kernel access and disclosure.\nI:H - The out-of-bounds scatterlist writes corrupt kernel memory and may permit control-flow hijacking or arbitrary modification if the attacker shapes the surrounding allocation state.\nA:H - The post-write BUG_ON reliably causes a kernel oops or panic, and malformed requests can be submitted repeatedly to disrupt the storage target."
}
]
}
],
"affected": [
{
"product": "Linux",
"vendor": "Linux",
"defaultStatus": "unaffected",
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"programFiles": [
"block/blk-mq.c"
],
"versions": [
{
"version": "76c313f658d2752e8527610677164aa7094ef7a5",
"lessThan": "53a01bcc0242590eda4c452a5bd996f62457113b",
"status": "affected",
"versionType": "git"
},
{
"version": "76c313f658d2752e8527610677164aa7094ef7a5",
"lessThan": "0943f81e1b3176f27dbaf6db268fc69d8a94f0ba",
"status": "affected",
"versionType": "git"
},
{
"version": "76c313f658d2752e8527610677164aa7094ef7a5",
"lessThan": "42929c98d044f126508baf54a65b0f87f932fa75",
"status": "affected",
"versionType": "git"
},
{
"version": "76c313f658d2752e8527610677164aa7094ef7a5",
"lessThan": "2c6e6a18a37b905cb584eb0dda3ae482162a81ca",
"status": "affected",
"versionType": "git"
}
]
},
{
"product": "Linux",
"vendor": "Linux",
"defaultStatus": "affected",
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"programFiles": [
"block/blk-mq.c"
],
"versions": [
{
"version": "6.12",
"status": "affected"
},
{
"version": "0",
"lessThan": "6.12",
"status": "unaffected",
"versionType": "semver"
},
{
"version": "6.12.92",
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"versionType": "semver"
},
{
"version": "6.18.34",
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"versionType": "semver"
},
{
"version": "7.0.11",
"lessThanOrEqual": "7.0.*",
"status": "unaffected",
"versionType": "semver"
},
{
"version": "7.1",
"lessThanOrEqual": "*",
"status": "unaffected",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"operator": "OR",
"negate": false,
"cpeMatch": [
{
"vulnerable": true,
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "6.12",
"versionEndExcluding": "6.12.92"
},
{
"vulnerable": true,
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "6.12",
"versionEndExcluding": "6.18.34"
},
{
"vulnerable": true,
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "6.12",
"versionEndExcluding": "7.0.11"
},
{
"vulnerable": true,
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "6.12",
"versionEndExcluding": "7.1"
}
]
}
]
}
],
"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"
}
},
"adp": [
{
"metrics": [
{
"other": {
"type": "ssvc",
"content": {
"id": "CVE-2026-64232",
"role": "CISA Coordinator",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "total"
}
],
"version": "2.0.3",
"timestamp": "2026-10-16T15:37:44.821934Z"
}
}
}
],
"problemTypes": [
{
"descriptions": [
{
"lang": "en",
"type": "CWE",
"cweId": "CWE-667",
"description": "CWE-667 Improper Locking"
}
]
}
],
"title": "CISA ADP Vulnrichment",
"providerMetadata": {
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP",
"dateUpdated": "2026-10-19T20:28:16.033Z"
}
}
]
}
}