Data corruption and memory disclosure via miscalculated offset
Published Apr 3, 2024 · Updated Aug 5, 2026
Out-of-bounds write in Linux nilfs2 allows local users to corrupt recovered file data and read uninitialized memory during mount recovery. The nilfs_recovery_copy_block() helper uses the source buffer-head offset instead of the recovered file position when copying a block into the page cache. Reachability requires a local user able to mount a nilfs2 filesystem with blocks smaller than a memory page after an unclean shutdown.
Summary
What happened
Out-of-bounds write in Linux nilfs2 allows local users to corrupt recovered file data and read uninitialized memory during mount recovery. The nilfs_recovery_copy_block() helper uses the source buffer-head offset instead of the recovered file position when copying a block into the page cache. Reachability requires a local user able to mount a nilfs2 filesystem with blocks smaller than a memory page after an unclean shutdown.
The record
- CVE
- CVE-2024-26697
- Published
- Apr 3, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- authenticated
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=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <120f7fa2008e3bd8b7680b4ab5df942decf60fd5
- Affected versionversion=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <2000016bab499074e6248ea85aeea7dd762355d9
- Affected versionversion=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <2e1480538ef60bfee5473dfe02b1ecbaf1a4aa0d
- Affected versionversion=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <364a66be2abdcd4fd426ffa44d9b8f40aafb3caa
- Affected versionversion=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <5278c3eb6bf5896417572b52adb6be9d26e92f65
- Affected versionversion=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <67b8bcbaed4777871bb0dcc888fb02a614a98ab1
- Affected versionversion=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <9c9c68d64fd3284f7097ed6ae057c8441f39fcd3
- Affected versionversion=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <a6efe6dbaaf504f5b3f8a5c3f711fe54e7dda0ba
- Affected versionversion=2.6.30
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