Kernel memory corruption via truncated inode size
Published Dec 27, 2024 · Updated Aug 5, 2026
Out-of-bounds memory access in Linux nilfs2 allows local users to read or corrupt kernel memory via a directory with a corrupted inode size. nilfs_last_byte() stores the 64-bit i_size in an unsigned int, discarding its upper 32 bits; nilfs_find_entry() then underflows its end calculation and scans beyond the folio. Reachability requires local access to the corrupted directory data and a lookup that traverses it; the resulting access can expose or alter data or crash the system.
Summary
What happened
Out-of-bounds memory access in Linux nilfs2 allows local users to read or corrupt kernel memory via a directory with a corrupted inode size. nilfs_last_byte() stores the 64-bit i_size in an unsigned int, discarding its upper 32 bits; nilfs_find_entry() then underflows its end calculation and scans beyond the folio. Reachability requires local access to the corrupted directory data and a lookup that traverses it; the resulting access can expose or alter data or crash the system.
The record
- CVE
- CVE-2024-56619
- Published
- Dec 27, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 27, 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=2.6.30
- Affected versionversion=2ba466d74ed74f073257f86e61519cb8f8f46184 <09d6d05579fd46e61abf6e457bb100ff11f3a9d3
- Affected versionversion=2ba466d74ed74f073257f86e61519cb8f8f46184 <31f7b57a77d4c82a34ddcb6ff35b5aa577ef153e
- Affected versionversion=2ba466d74ed74f073257f86e61519cb8f8f46184 <48eb6e7404948032bbe811c5affbe39f6b316951
- Affected versionversion=2ba466d74ed74f073257f86e61519cb8f8f46184 <5af8366625182f01f6d8465c9a3210574673af57
- Affected versionversion=2ba466d74ed74f073257f86e61519cb8f8f46184 <985ebec4ab0a28bb5910c3b1481a40fbf7f9e61d
- Affected versionversion=2ba466d74ed74f073257f86e61519cb8f8f46184 <c3afea07477baccdbdec4483f8d5e59d42a3f67f
- Affected versionversion=2ba466d74ed74f073257f86e61519cb8f8f46184 <e3732102a9d638d8627d14fdf7b208462f0520e0
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