Kernel-memory disclosure or crash via negative checksum length
Published Oct 22, 2025 · Updated Oct 22, 2025
Out-of-bounds read in arm64 checksum code in affected Linux 5.6 through 6.5 releases allows local users to disclose kernel memory or crash the host. The do_csum function accepts an attacker-controlled negative length, performs an undefined shift, and walks beyond the intended buffer while calculating a packet checksum. A local process with AF_PACKET access can trigger the TX GSO path without user interaction; the resulting checksum exposes a function of kernel memory, while sufficiently large reads can panic or oops the host.
Summary
What happened
Out-of-bounds read in arm64 checksum code in affected Linux 5.6 through 6.5 releases allows local users to disclose kernel memory or crash the host. The do_csum function accepts an attacker-controlled negative length, performs an undefined shift, and walks beyond the intended buffer while calculating a packet checksum. A local process with AF_PACKET access can trigger the TX GSO path without user interaction; the resulting checksum exposes a function of kernel memory, while sufficiently large reads can panic or oops the host.
The record
- CVE
- CVE-2023-53726
- Published
- Oct 22, 2025
- Updated
- Oct 22, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 22, 2025CVE publishedPublication date reported by the CVE source.
- Oct 22, 2025Record 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=5.6
- Affected versionversion=5777eaed566a1d63e344d3dd8f2b5e33be20643e <5a85727239a23de1cc8d93985f1056308128f3e2
- Affected versionversion=5777eaed566a1d63e344d3dd8f2b5e33be20643e <8bd795fedb8450ecbef18eeadbd23ed8fc7630f5
- Affected versionversion=5777eaed566a1d63e344d3dd8f2b5e33be20643e <9a43563cfd6b9200ff2f76b3f9fcdcb217ceb523
- Affected versionversion=5777eaed566a1d63e344d3dd8f2b5e33be20643e <a5ad2f87d8e74e351d3f500ad9d5b3a5653e1c6f
- Affected versionversion=5777eaed566a1d63e344d3dd8f2b5e33be20643e <ba0b46166b8e547024d02345a68b747841931ad2
- Affected versionversion=5777eaed566a1d63e344d3dd8f2b5e33be20643e <fcdf904e866de0e3715835e50409fda3b2590527
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