CVE-2024-42105nilfs2: fix inode number range checks
- 7.8HighCVSS base score
- 0.26%Exploitation in 30 daysEPSS · top 82% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix inode number range checks Patch series "nilfs2: fix potential issues related to reserved inodes". This series fixes one use-after-free issue reported by syzbot, caused by nilfs2's internal inode being exposed in the namespace on a corrupted filesystem, and a couple of flaws that cause problems if the starting number of non-reserved inodes written in the on-disk super block is intentionally (or corruptly) changed from its default value. This patch (of 3): In the current implementation of nilfs2, "nilfs->ns_first_ino", which gives the first non-reserved inode number, is read from the superblock, but its lower limit is not checked. As a result, if a number that overlaps with the inode number range of reserved inodes such as the root directory or metadata files is set in the super block parameter, the inode number test macros (NILFS_MDT_INODE and NILFS_VALID_INODE) will not function properly. In addition, these test macros use left bit-shift calculations using with the inode number as the shift count via the BIT macro, but the result of a shift calculation that exceeds the bit width of an integer is undefined in the C specification, so if "ns_first_ino" is set to a large value other than the default value NILFS_USER_INO (=11), the macros may potentially malfunction depending on the environment. Fix these issues by checking the lower bound of "nilfs->ns_first_ino" and by preventing bit shifts equal to or greater than the NILFS_USER_INO constant in the inode number test macros. Also, change the type of "ns_first_ino" from signed integer to unsigned integer to avoid the need for type casting in comparisons such as the lower bound check introduced this time.
Timeline
ID reserved
By Linux
- 1 day later
· 1 day later
Published
- 2 years later
· 2 years later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.26% · top 82% of all CVEs (19 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f – < 57235c3c88bb430043728d0d02f44a4efe386476
- affected 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f – < 08cab183a624ba71603f3754643ae11cab34dbc4
- affected 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f – < 731011ac6c37cbe97ece229fc6daa486276052c5
- affected 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f – < 3be4dcc8d7bea52ea41f87aa4bbf959efe7a5987
- affected 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f – < fae1959d6ab2c52677b113935e36ab4e25df37ea
- affected 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f – < 9194f8ca57527958bee207919458e372d638d783
- affected 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f – < 1c91058425a01131ea30dda6cf43c67b17884d6a
- affected 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f – < e2fec219a36e0993642844be0f345513507031f4
- affected 2.6.30
- unaffected < 2.6.30
- unaffected 4.19.318 – ≤ 4.19.*
- unaffected 5.4.280 – ≤ 5.4.*
- unaffected 5.10.222 – ≤ 5.10.*
- unaffected 5.15.163 – ≤ 5.15.*
- unaffected 6.1.98 – ≤ 6.1.*
- unaffected 6.6.39 – ≤ 6.6.*
- unaffected 6.9.9 – ≤ 6.9.*
- unaffected 6.10 – ≤ *
References
References9
- https://git.kernel.org/stable/c/57235c3c88bb430043728d0d02f44a4efe386476 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/08cab183a624ba71603f3754643ae11cab34dbc4 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/731011ac6c37cbe97ece229fc6daa486276052c5 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/3be4dcc8d7bea52ea41f87aa4bbf959efe7a5987 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/fae1959d6ab2c52677b113935e36ab4e25df37ea (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/9194f8ca57527958bee207919458e372d638d783 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/1c91058425a01131ea30dda6cf43c67b17884d6a (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/e2fec219a36e0993642844be0f345513507031f4 (opens in a new tab)x_transferred
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-39937 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-42105)Record last updated .