Local kernel compromise via stale buffer clearing
Published Feb 27, 2025 · Updated Aug 5, 2026
Use-after-free in the nilfs2 filesystem in Linux allows local users to corrupt kernel memory through a malformed mounted volume. During read-only fallback, nilfs2 page-write callbacks clear busy buffer states without first checking whether another path still references the buffer, allowing the buffer-head ring to be freed while it remains in use. An unprivileged user must reach an already mounted nilfs2 volume and coordinate ordinary filesystem operations with writeback; exploitation can disclose or alter kernel memory, corrupt filesystem data, crash the kernel, or hang filesystem activity.
Summary
What happened
Use-after-free in the nilfs2 filesystem in Linux allows local users to corrupt kernel memory through a malformed mounted volume. During read-only fallback, nilfs2 page-write callbacks clear busy buffer states without first checking whether another path still references the buffer, allowing the buffer-head ring to be freed while it remains in use. An unprivileged user must reach an already mounted nilfs2 volume and coordinate ordinary filesystem operations with writeback; exploitation can disclose or alter kernel memory, corrupt filesystem data, crash the kernel, or hang filesystem activity.
The record
- CVE
- CVE-2025-21722
- Published
- Feb 27, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 27, 2025CVE 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=3.10
- Affected versionversion=8c26c4e2694a163d525976e804d81cd955bbb40c <1098bb8d52419d262a3358d099a1598a920b730f
- Affected versionversion=8c26c4e2694a163d525976e804d81cd955bbb40c <19296737024cd220a1d6590bf4c092bca8c99497
- Affected versionversion=8c26c4e2694a163d525976e804d81cd955bbb40c <4d042811c72f71be7c14726db2c72b67025a7cb5
- Affected versionversion=8c26c4e2694a163d525976e804d81cd955bbb40c <557ccf5e49f1fb848a29698585bcab2e50a597ef
- Affected versionversion=8c26c4e2694a163d525976e804d81cd955bbb40c <7d0544bacc11d6aa26ecd7debf9353193c7a3328
- Affected versionversion=8c26c4e2694a163d525976e804d81cd955bbb40c <ca76bb226bf47ff04c782cacbd299f12ddee1ec1
- Affected versionversion=8c26c4e2694a163d525976e804d81cd955bbb40c <f51ff43c4c5a6c8e72d0aca89e4d5e688938412f
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