CVE-2024-42105: nilfs2: fix inode number range checks
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 08cab183a624ba71603f3754643ae11cab34dbc4, 1c91058425a01131ea30dda6cf43c67b17884d6a, 3be4dcc8d7bea52ea41f87aa4bbf959efe7a5987.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 08cab183a624ba71603f3754643ae11cab34dbc4, 1c91058425a01131ea30dda6cf43c67b17884d6a, 3be4dcc8d7bea52ea41f87aa4bbf959efe7a5987 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 30, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 17th percentile
- CWE
- CWE-416
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.30affected
- 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f and later · before 57235c3c88bb430043728d0d02f44a4efe386476affected · git
- 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f and later · before 08cab183a624ba71603f3754643ae11cab34dbc4affected · git
- 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f and later · before 731011ac6c37cbe97ece229fc6daa486276052c5affected · git
- 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f and later · before 3be4dcc8d7bea52ea41f87aa4bbf959efe7a5987affected · git
- 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f and later · before fae1959d6ab2c52677b113935e36ab4e25df37eaaffected · git
- 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f and later · before 9194f8ca57527958bee207919458e372d638d783affected · git
- 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f and later · before 1c91058425a01131ea30dda6cf43c67b17884d6aaffected · git
- 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f and later · before e2fec219a36e0993642844be0f345513507031f4affected · git
- before 2.6.30not affected · semver
Affected versions · NVD (8)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 4.19.318
- linux linux kernel4.20 and later · before 5.4.280
- linux linux kernel5.5 and later · before 5.10.222
- linux linux kernel5.11 and later · before 5.15.163
- linux linux kernel5.16 and later · before 6.1.98
- linux linux kernel6.2 and later · before 6.6.39
- linux linux kernel6.7 and later · before 6.9.9
- linux linux kernel6.10
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.98-1 | 6.1.98-1 |
| Debian:13 | linux | before 6.9.9-1 | 6.9.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-42103Jul 30, 2024 · btrfs: fix adding block group to a reclaim list and the unused list during reclaim22Monitor
- ← EarlierCVE-2024-42104Jul 30, 2024 · nilfs2: add missing check for inode numbers on directory entries31Monitor
- Later →CVE-2024-42108Jul 30, 2024 · net: rswitch: Avoid use-after-free in rswitch_poll()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 08cab183a624ba71603f3754643ae11cab34dbc4 | Vendor (CNA) |
| Linux Linux | 1c91058425a01131ea30dda6cf43c67b17884d6a | Vendor (CNA) |
| Linux Linux | 3be4dcc8d7bea52ea41f87aa4bbf959efe7a5987 | Vendor (CNA) |
| Linux Linux | 57235c3c88bb430043728d0d02f44a4efe386476 | Vendor (CNA) |
| Linux Linux | 731011ac6c37cbe97ece229fc6daa486276052c5 | Vendor (CNA) |
| Linux Linux | 9194f8ca57527958bee207919458e372d638d783 | Vendor (CNA) |
| Linux Linux | e2fec219a36e0993642844be0f345513507031f4 | Vendor (CNA) |
| Linux Linux | fae1959d6ab2c52677b113935e36ab4e25df37ea | Vendor (CNA) |
| debian:linux | 6.1.98-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1106 · Jul 31, 2024(Linux Kernel Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/1c91058425a01131ea30dda6cf43c67b17884d6a
- git.kernel.org/stable/c/3be4dcc8d7bea52ea41f87aa4bbf959efe7a5987
- git.kernel.org/stable/c/57235c3c88bb430043728d0d02f44a4efe386476
- git.kernel.org/stable/c/731011ac6c37cbe97ece229fc6daa486276052c5
- git.kernel.org/stable/c/9194f8ca57527958bee207919458e372d638d783
- git.kernel.org/stable/c/e2fec219a36e0993642844be0f345513507031f4
- git.kernel.org/stable/c/fae1959d6ab2c52677b113935e36ab4e25df37ea
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.