CVE-2025-71292 Details
Description
In the Linux kernel, the following vulnerability has been resolved: jfs: nlink overflow in jfs_rename If nlink is maximal for a directory (-1) and inside that directory you perform a rename for some child directory (not moving from the parent), then the nlink of the first directory is first incremented and later decremented. Normally this is fine, but when nlink = -1 this causes a wrap around to 0, and then drop_nlink issues a warning. After applying the patch syzbot no longer issues any warnings. I also ran some basic fs tests to look for any regressions.
A vulnerability in the JFS (Journaled File System) component of the Linux kernel has been identified, related to how directory link counts (nlink) are managed during rename operations. This issue occurs when a directory's nlink value is at its maximum (-1), and a child directory is renamed within it without changing its parent. The nlink count of the original directory is incorrectly wrapped from -1 to 0, triggering a warning. This vulnerability affects the Linux kernel's stable group, specifically in versions prior to the patch that addresses this issue.
Users can apply the patch available in the Linux kernel stable tree to address this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/2108829a59f081e822fdab8c2cd7131deb8aa8a1 | kernel.org | Patch |
| https://git.kernel.org/stable/c/5d77c36cd4b698649f5c30c5f6c084f4f61d1880 | kernel.org | Patch |
| https://git.kernel.org/stable/c/9218dc26fd922b09858ecd3666ed57dfd8098da8 | kernel.org | Patch |
| https://git.kernel.org/stable/c/93c325746ae59709b4f9bad4e3e4761c8d566c70 | kernel.org | Patch |
| https://git.kernel.org/stable/c/a3d66089e50a6e0142f8884471f74292102ea9aa | kernel.org | Patch |
| https://git.kernel.org/stable/c/b4330a0d0947fbdc9d445cbbeabd8cc910a8c9ca | kernel.org | Patch |
| https://git.kernel.org/stable/c/f70fcbc2ac7c24f087a2c895c5753aa730b1e479 | kernel.org | Patch |
| https://git.kernel.org/stable/c/fe136426e30ca6debcf916fd6a141555ed9fde74 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 2.6.12.1, < 5.10.252 >= 5.11, < 5.15.202 >= 5.16, < 6.1.165 >= 6.2, < 6.6.128 >= 6.7, < 6.12.75 >= 6.13, < 6.18.16 >= 6.19, < 6.19.6 2.6.12 - 2.6.12 rc2 2.6.12 rc3 2.6.12 rc4 2.6.12 rc5 2.6.12 rc6 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 30, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| May 13, 2026 | Initial Analysis | [email protected] |
| May 6, 2026 | New CVE Received | kernel.org |