Kernel memory corruption via undersized AFS buffer
Published Apr 3, 2024 · Updated Aug 5, 2026
Out-of-bounds write in the Linux kernel AFS client 4.15 and later allows remote attackers to corrupt kernel memory through AFS replies. The afs_update_volume_status() function uses sprintf() to place a decimal volume identifier in a 16-byte stack buffer, although the stated maximum requires 21 bytes including termination. Reachability requires a malicious or spoofed AFS server response, but current CNA analysis finds the wire identifier limited to 32 bits and therefore too short to overflow the buffer.
Summary
What happened
Out-of-bounds write in the Linux kernel AFS client 4.15 and later allows remote attackers to corrupt kernel memory through AFS replies. The afs_update_volume_status() function uses sprintf() to place a decimal volume identifier in a 16-byte stack buffer, although the stated maximum requires 21 bytes including termination. Reachability requires a malicious or spoofed AFS server response, but current CNA analysis finds the wire identifier limited to 32 bits and therefore too short to overflow the buffer.
The record
- CVE
- CVE-2024-26736
- Published
- Apr 3, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 3, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=4.15
- Affected versionversion=d2ddc776a4581d900fc3bdc7803b403daae64d88 <5c27d85a69fa16a08813ba37ddfb4bbc9a1ed6b5
- Affected versionversion=d2ddc776a4581d900fc3bdc7803b403daae64d88 <6e6065dd25b661420fac19c34282b6c626fcd35e
- Affected versionversion=d2ddc776a4581d900fc3bdc7803b403daae64d88 <6ea38e2aeb72349cad50e38899b0ba6fbcb2af3d
- Affected versionversion=d2ddc776a4581d900fc3bdc7803b403daae64d88 <d34a5e57632bb5ff825196ddd9a48ca403626dfa
- Affected versionversion=d2ddc776a4581d900fc3bdc7803b403daae64d88 <d9b5e2b7a8196850383c70d099bfd39e81ab6637
- Affected versionversion=d2ddc776a4581d900fc3bdc7803b403daae64d88 <e56662160fc24d28cb75ac095cc6415ae1bda43e
- Affected versionversion=d2ddc776a4581d900fc3bdc7803b403daae64d88 <e8530b170e464017203e3b8c6c49af6e916aece1
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.
Weakness, pattern, technique
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