Memory corruption via stale integrity segment count
Published Jul 24, 2026 · Updated Jul 24, 2026
Memory corruption in the Linux Kernel block subsystem allows remote attackers to crash the host through crafted storage I/O. blk_insert_cloned_request retains the source request’s integrity-segment count even when a lower queue’s tighter limits split the data into more segments, so blk_rq_map_integrity_sg writes past the undersized scatterlist before its BUG_ON fires. Reachability requires a PI-enabled iSER or NVMe/RDMA target over request-based dm-multipath; an unauthenticated initiator is possible only when target access controls permit it, and successful triggering corrupts kernel memory and can panic the host.
Summary
What happened
Memory corruption in the Linux Kernel block subsystem allows remote attackers to crash the host through crafted storage I/O. blk_insert_cloned_request retains the source request’s integrity-segment count even when a lower queue’s tighter limits split the data into more segments, so blk_rq_map_integrity_sg writes past the undersized scatterlist before its BUG_ON fires. Reachability requires a PI-enabled iSER or NVMe/RDMA target over request-based dm-multipath; an unauthenticated initiator is possible only when target access controls permit it, and successful triggering corrupts kernel memory and can panic the host.
The record
- CVE
- CVE-2026-64232
- Published
- Jul 24, 2026
- Updated
- Jul 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-617, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 24, 2026CVE publishedPublication date reported by the CVE source.
- Jul 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.12
- Affected versionversion=76c313f658d2752e8527610677164aa7094ef7a5 <0943f81e1b3176f27dbaf6db268fc69d8a94f0ba
- Affected versionversion=76c313f658d2752e8527610677164aa7094ef7a5 <2c6e6a18a37b905cb584eb0dda3ae482162a81ca
- Affected versionversion=76c313f658d2752e8527610677164aa7094ef7a5 <42929c98d044f126508baf54a65b0f87f932fa75
- Affected versionversion=76c313f658d2752e8527610677164aa7094ef7a5 <53a01bcc0242590eda4c452a5bd996f62457113b
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo