Answer in brief
CVE-2024-42105 records a High severity (CVSS 7.8) vulnerability in nilfs2: fix inode number range checks. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=8a9d2191e9f43bbcd256a9a6871bd73434c83f2f <57235c3c88bb430043728d0d02f44a4efe386476 || >=8a9d2191e9f43bbcd256a9a6871bd73434c83f2f <08cab183a624ba71603f3754643ae11cab34dbc4 || >=8a9d2191e9f43bbcd256a9a6871bd73434c83f2f <731011ac6c37cbe97ece229fc6daa486276052c5 || >=8a9d2191e9f43bbcd256a9a6871bd73434c83f2f <3be4dcc8d7bea52ea41f87aa4bbf959efe7a5987 || >=8a9d2191e9f43bbcd256a9a6871bd73434c83f2f <fae1959d6ab2c52677b113935e36ab4e25df37ea || >=8a9d2191e9f43bbcd256a9a6871bd73434c83f2f <9194f8ca57527958bee207919458e372d638d783 || >=8a9d2191e9f43bbcd256a9a6871bd73434c83f2f <1c91058425a01131ea30dda6cf43c67b17884d6a || >=8a9d2191e9f43bbcd256a9a6871bd73434c83f2f <e2fec219a36e0993642844be0f345513507031f4 | 57235c3c88bb430043728d0d02f44a4efe386476, 08cab183a624ba71603f3754643ae11cab34dbc4, 731011ac6c37cbe97ece229fc6daa486276052c5, 3be4dcc8d7bea52ea41f87aa4bbf959efe7a5987, fae1959d6ab2c52677b113935e36ab4e25df37ea, 9194f8ca57527958bee207919458e372d638d783, 1c91058425a01131ea30dda6cf43c67b17884d6a, e2fec219a36e0993642844be0f345513507031f4 |
| Linux/Linuxgeneric | 2.6.30 | Not reported |
Published upstream
Jul 30, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.