CVE-2026-64232

{"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"}}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CISA ADP Vulnrichment", "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"}]}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-10-16T15:37:45.475Z"}}], "cna": {"title": "block: recompute nr_integrity_segments in blk_insert_cloned_request", "metrics": [{"cvssV3_1": {"version": "3.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"}, "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": [{"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "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"}], "programFiles": ["block/blk-mq.c"], "defaultStatus": "unaffected"}, {"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "6.12"}, {"status": "unaffected", "version": "0", "lessThan": "6.12", "versionType": "semver"}, {"status": "unaffected", "version": "6.12.92", "versionType": "semver", "lessThanOrEqual": "6.12.*"}, {"status": "unaffected", "version": "6.18.34", "versionType": "semver", "lessThanOrEqual": "6.18.*"}, {"status": "unaffected", "version": "7.0.11", "versionType": "semver", "lessThanOrEqual": "7.0.*"}, {"status": "unaffected", "version": "7.1", "versionType": "original_commit_for_fix", "lessThanOrEqual": "*"}], "programFiles": ["block/blk-mq.c"], "defaultStatus": "affected"}], "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"}], "x_generator": {"engine": "bippy-1.2.0"}, "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."}], "cpeApplicability": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "6.12.92", "versionStartIncluding": "6.12"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "6.18.34", "versionStartIncluding": "6.12"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "7.0.11", "versionStartIncluding": "6.12"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "7.1", "versionStartIncluding": "6.12"}], "operator": "OR"}]}], "providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-08-05T12:40:12.752Z"}}}, "cveMetadata": {"cveId": "CVE-2026-64232", "state": "PUBLISHED", "dateUpdated": "2026-10-19T20:28:16.033Z", "dateReserved": "2026-07-19T15:36:31.771Z", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "datePublished": "2026-07-24T15:23:13.729Z", "assignerShortName": "Linux"}, "dataVersion": "5.2"}

{"affected": [{"affectedData": [{"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"}]}], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "matchCriteriaId": "9574AA5E-61DC-4F38-82BC-69F89AA7593C", "versionEndExcluding": "6.12.92", "versionStartIncluding": "6.12", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "matchCriteriaId": "A4B1EF6D-18D7-4838-BC37-7499D5DCC3C0", "versionEndExcluding": "6.18.34", "versionStartIncluding": "6.13", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "matchCriteriaId": "0520D091-FC52-4A50-AF07-70AE7D08B750", "versionEndExcluding": "7.0.11", "versionStartIncluding": "6.19", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:*", "matchCriteriaId": "B1EF7059-E670-45F4-B422-54C40FA86390", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:*", "matchCriteriaId": "0D38F0BF-A728-4133-A358-D44A2F7EE6D6", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:*", "matchCriteriaId": "EC732D08-5F7B-46D9-B154-E60C7F4F0A97", "vulnerable": true}], "negate": false, "operator": "OR"}]}], "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'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."}, {"lang": "es", "value": "En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\n\nblock: recalcular nr_integrity_segments en blk_insert_cloned_request\n\nblk_insert_cloned_request() ya recalcula nr_phys_segments contra la cola inferior, porque \u2019la configuraci\u00f3n de la cola relacionada con el conteo de segmentos puede diferir de la cola original.\u2019 El mismo razonamiento exacto se aplica a los segmentos de integridad: la cola subyacente de un controlador apilado puede tener un virt_boundary_mask, seg_boundary_mask o max_segment_size m\u00e1s estricto que la cola superior, en cuyo caso blk_rq_count_integrity_sg() contra la cola inferior produce un conteo diferente que el rq -> nr_integrity_segments en cach\u00e9 heredado de la solicitud de origen por blk_rq_prep_clone().\n\nCuando el conteo en cach\u00e9 es menor que el conteo real de la cola inferior, blk_rq_map_integrity_sg() activa\n\n\tBUG_ON(segments > rq -> nr_integrity_segments);\n\nen el despacho. Las mismas familias de configuraciones apiladas que motivaron el rec\u00e1lculo existente de nr_phys_segments -- dm-multipath que se ramifica a nvme-rdma en particular -- pueden producir esto.\n\nReflejar el manejo de nr_phys_segments: cuando la solicitud lleva integridad, recalcular nr_integrity_segments contra la cola inferior y rechazar la solicitud si excede el max_integrity_segments de la cola inferior. blk_rq_count_integrity_sg() y queue_max_integrity_segments() ya est\u00e1n disponibles ambos a trav\u00e9s de <linux/blk-integrity.h>, que blk-mq.c incluye.\n\nEsto cierra una brecha latente en el contrato de apilamiento y alinea la contabilidad de segmentos de integridad con la contabilidad existente de segmentos f\u00edsicos."}], "id": "CVE-2026-64232", "lastModified": "2026-11-08T20:10:00.187", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "baseScore": 9.8, "baseSeverity": "CRITICAL", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "version": "3.1"}, "exploitabilityScore": 3.9, "impactScore": 5.9, "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "type": "Secondary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-64232", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "total"}], "role": "CISA Coordinator", "timestamp": "2026-10-16T15:37:44.821934Z", "version": "2.0.3"}}]}, "published": "2026-07-24T16:16:52.367", "references": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "tags": ["Patch"], "url": "https://git.kernel.org/stable/c/0943f81e1b3176f27dbaf6db268fc69d8a94f0ba"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "tags": ["Patch"], "url": "https://git.kernel.org/stable/c/2c6e6a18a37b905cb584eb0dda3ae482162a81ca"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "tags": ["Patch"], "url": "https://git.kernel.org/stable/c/42929c98d044f126508baf54a65b0f87f932fa75"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "tags": ["Patch"], "url": "https://git.kernel.org/stable/c/53a01bcc0242590eda4c452a5bd996f62457113b"}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "vulnStatus": "Modified", "weaknesses": [{"description": [{"lang": "en", "value": "NVD-CWE-noinfo"}], "source": "nvd@nist.gov", "type": "Primary"}, {"description": [{"lang": "en", "value": "CWE-667"}], "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "type": "Secondary"}]}

{"bugzilla": {"description": "kernel: block: recompute nr_integrity_segments in blk_insert_cloned_request", "id": "2506791", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2506791"}, "csaw": false, "cvss3": {"cvss3_base_score": "5.5", "cvss3_scoring_vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H", "status": "draft"}, "details": ["No description is available for this CVE."], "name": "CVE-2026-64232", "package_state": [{"cpe": "cpe:/o:redhat:enterprise_linux:10", "fix_state": "Fix deferred", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 10"}, {"cpe": "cpe:/o:redhat:enterprise_linux:6", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 6"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Fix deferred", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 9"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Fix deferred", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 9"}], "public_date": "2026-07-24T00:00:00Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2026-64232\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-64232\nhttps://lore.kernel.org/linux-cve-announce/2026072419-CVE-2026-64232-51ea@gregkh/T"], "threat_severity": "Low"}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "code_commit", "value": "[76c313f658d2752e8527610677164aa7094ef7a5,53a01bcc0242590eda4c452a5bd996f62457113b)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "code_commit", "value": "[76c313f658d2752e8527610677164aa7094ef7a5,0943f81e1b3176f27dbaf6db268fc69d8a94f0ba)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "code_commit", "value": "[76c313f658d2752e8527610677164aa7094ef7a5,42929c98d044f126508baf54a65b0f87f932fa75)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "code_commit", "value": "[76c313f658d2752e8527610677164aa7094ef7a5,2c6e6a18a37b905cb584eb0dda3ae482162a81ca)"}}], "enrichment": {"confidence": 99.0, "confidence_source": "inferred", "scores": [{"score": 99.0, "source": "inferred"}, {"score": 100.0, "source": "matching"}]}, "original": {"product": "Linux", "source": "cna", "vendor": "Linux"}, "product": "linux_kernel", "vendor": "linux"}, {"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "generic", "value": "6.12"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "generic", "value": "[0,6.12)"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "semver", "value": "[6.12.92,6.13.0)"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "semver", "value": "[6.18.34,6.19.0)"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "semver", "value": "[7.0.11,7.1.0)"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "generic", "value": "[7.1,*]"}}], "enrichment": {"confidence": 99.0, "confidence_source": "inferred", "scores": [{"score": 99.0, "source": "inferred"}, {"score": 100.0, "source": "matching"}]}, "original": {"product": "Linux", "source": "cna", "vendor": "Linux"}, "product": "linux_kernel", "vendor": "linux"}], "created": "2026-07-24T21:15:02.717872+00:00", "updated": "2026-10-20T09:30:12.554755+00:00", "vendors": ["linux", "linux$PRODUCT$linux_kernel"]}