Service interruption via JFS link-count wraparound
Published May 6, 2026 · Updated May 6, 2026
Integer overflow in Linux Kernel JFS allows remote attackers to interrupt service through a rename on an exported writable directory. In jfs_rename, a same-parent child-directory rename increments a maximal 0xffffffff parent link count, wraps it to zero, and makes drop_nlink emit a warning before the later decrement restores the count. Remote reachability requires JFS to be exported over NFS with anonymous write permission; repeated warnings consume resources, and panic-on-warning configurations can crash the host.
Summary
What happened
Integer overflow in Linux Kernel JFS allows remote attackers to interrupt service through a rename on an exported writable directory. In jfs_rename, a same-parent child-directory rename increments a maximal 0xffffffff parent link count, wraps it to zero, and makes drop_nlink emit a warning before the later decrement restores the count. Remote reachability requires JFS to be exported over NFS with anonymous write permission; repeated warnings consume resources, and panic-on-warning configurations can crash the host.
The record
- CVE
- CVE-2025-71292
- Published
- May 6, 2026
- Updated
- May 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 6, 2026CVE publishedPublication date reported by the CVE source.
- May 6, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2108829a59f081e822fdab8c2cd7131deb8aa8a1
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5d77c36cd4b698649f5c30c5f6c084f4f61d1880
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9218dc26fd922b09858ecd3666ed57dfd8098da8
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <93c325746ae59709b4f9bad4e3e4761c8d566c70
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a3d66089e50a6e0142f8884471f74292102ea9aa
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b4330a0d0947fbdc9d445cbbeabd8cc910a8c9ca
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f70fcbc2ac7c24f087a2c895c5753aa730b1e479
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fe136426e30ca6debcf916fd6a141555ed9fde74
What conditions does exploitation require?
What is affected?
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