Local service interruption via F2FS rename leak
Published May 1, 2026 · Updated May 1, 2026
Memory exhaustion in the F2FS rename path in Linux Kernel allows local users to interrupt service through repeated rename operations. f2fs_rename calls f2fs_setup_filename while preparing a whiteout but omits the matching f2fs_free_filename release, leaking each allocated filename object. A local user must be able to rename entries on an affected F2FS filesystem; sustained triggering consumes kernel memory until host availability is disrupted, without exposing or altering protected data.
Summary
What happened
Memory exhaustion in the F2FS rename path in Linux Kernel allows local users to interrupt service through repeated rename operations. f2fs_rename calls f2fs_setup_filename while preparing a whiteout but omits the matching f2fs_free_filename release, leaking each allocated filename object. A local user must be able to rename entries on an affected F2FS filesystem; sustained triggering consumes kernel memory until host availability is disrupted, without exposing or altering protected data.
The record
- CVE
- CVE-2026-31714
- Published
- May 1, 2026
- Updated
- May 1, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-401, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2026CVE publishedPublication date reported by the CVE source.
- May 1, 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=1d1b89c9846e6a550eca3d2ce9323fb591e4f321
- Affected versionversion=40b2d55e045222dd6de2a54a299f682e0f954b03 <047c0aef6af37a2a35181aa085c616ad286386f1
- Affected versionversion=40b2d55e045222dd6de2a54a299f682e0f954b03 <369eb2016d8e2f01931b3bad1cb9cefa83f44003
- Affected versionversion=40b2d55e045222dd6de2a54a299f682e0f954b03 <3cf11e6f36c170050c12171dd6fd3142711478fc
- Affected versionversion=40b2d55e045222dd6de2a54a299f682e0f954b03 <c78206dcb912ab60b8ee3cbe8c48d749a9a12e1e
- Affected versionversion=64582cc5357cd984724cfb0835b4a34d9c279d31
- Affected versionversion=6.9
- Affected versionversion=7525dec4b34c80b3015c3f2ac143fd2bfc1febc3 <a76c1cad4e80a9802ef8048662255417e3ce5b79
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