NVD / CVE Program· CNA Linux

CVE-2024-42104: nilfs2: add missing check for inode numbers on directory entries

HighCVSS 7.8 · v3.1—No exploit Fix available

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 07c176e7acc5579c133bb923ab21316d192d0a95, 1b7d549ed2c1fa202c751b69423a0d3a6bd5a180, 265fff1a01cdc083aeaf0d934c929db5cc64aebf.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 07c176e7acc5579c133bb923ab21316d192d0a95, 1b7d549ed2c1fa202c751b69423a0d3a6bd5a180, 265fff1a01cdc083aeaf0d934c929db5cc64aebf 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: add missing check for inode numbers on directory entries Syzbot reported that mounting and unmounting a specific pattern of corrupted nilfs2 filesystem images causes a use-after-free of metadata file inodes, which triggers a kernel bug in lru_add_fn(). As Jan Kara pointed out, this is because the link count of a metadata file gets corrupted to 0, and nilfs_evict_inode(), which is called from iput(), tries to delete that inode (ifile inode in this case). The inconsistency occurs because directories containing the inode numbers of these metadata files that should not be visible in the namespace are read without checking. Fix this issue by treating the inode numbers of these internal files as errors in the sanity check helper when reading directory folios/pages. Also thanks to Hillf Danton and Matthew Wilcox for their initial mm-layer analysis.

Memory safety

Published: Jul 30, 2024
Updated: Aug 5, 2026
EPSS: 0.2% · 17th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

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 it

Noroxi 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 help

Affected 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
- 2ba466d74ed74f073257f86e61519cb8f8f46184 and later · before c33c2b0d92aa1c2262d999b2598ad6fbd53bd479affected · git
- 2ba466d74ed74f073257f86e61519cb8f8f46184 and later · before 07c176e7acc5579c133bb923ab21316d192d0a95affected · git
- 2ba466d74ed74f073257f86e61519cb8f8f46184 and later · before 2f2fa9cf7c3537958a82fbe8c8595a5eb0861ad7affected · git
- 2ba466d74ed74f073257f86e61519cb8f8f46184 and later · before b11e8fb93ea5eefb2e4e719497ea177a58ff6131affected · git
- 2ba466d74ed74f073257f86e61519cb8f8f46184 and later · before 1b7d549ed2c1fa202c751b69423a0d3a6bd5a180affected · git
- 2ba466d74ed74f073257f86e61519cb8f8f46184 and later · before 3ab40870edb883b9633dc5cd55f5a2a11afa618daffected · git
- 2ba466d74ed74f073257f86e61519cb8f8f46184 and later · before 265fff1a01cdc083aeaf0d934c929db5cc64aebfaffected · git
- 2ba466d74ed74f073257f86e61519cb8f8f46184 and later · before bb76c6c274683c8570ad788f79d4b875bde0e458affected · git
- before 2.6.30not affected · semver

Affected versions · NVD (7)

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

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
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	kernel-default	before 3.0.101-108.165.1	3.0.101-108.165.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	kernel-ec2	before 3.0.101-108.165.1	3.0.101-108.165.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	kernel-source	before 3.0.101-108.165.1	3.0.101-108.165.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	kernel-syms	before 3.0.101-108.165.1	3.0.101-108.165.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	kernel-trace	before 3.0.101-108.165.1	3.0.101-108.165.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	kernel-xen	before 3.0.101-108.165.1	3.0.101-108.165.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
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…KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2024-42102Jul 30, 2024 · Revert "mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again"
18Monitor
← EarlierCVE-2024-42103Jul 30, 2024 · btrfs: fix adding block group to a reclaim list and the unused list during reclaim
22Monitor
Later →CVE-2024-42105Jul 30, 2024 · nilfs2: fix inode number range checks
31Monitor

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	07c176e7acc5579c133bb923ab21316d192d0a95	Vendor (CNA)
Linux Linux	1b7d549ed2c1fa202c751b69423a0d3a6bd5a180	Vendor (CNA)
Linux Linux	265fff1a01cdc083aeaf0d934c929db5cc64aebf	Vendor (CNA)
Linux Linux	2f2fa9cf7c3537958a82fbe8c8595a5eb0861ad7	Vendor (CNA)
Linux Linux	3ab40870edb883b9633dc5cd55f5a2a11afa618d	Vendor (CNA)
Linux Linux	b11e8fb93ea5eefb2e4e719497ea177a58ff6131	Vendor (CNA)
Linux Linux	bb76c6c274683c8570ad788f79d4b875bde0e458	Vendor (CNA)
Linux Linux	c33c2b0d92aa1c2262d999b2598ad6fbd53bd479	Vendor (CNA)
debian:linux	6.1.98-1 · Debian:12	Package registry (OSV)
suse:kernel-default	3.0.101-108.165.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	Package registry (OSV)
suse:kernel-ec2	3.0.101-108.165.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	Package registry (OSV)
suse:kernel-source	3.0.101-108.165.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	Package registry (OSV)
suse:kernel-syms	3.0.101-108.165.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	Package registry (OSV)
suse:kernel-trace	3.0.101-108.165.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	Package registry (OSV)
suse:kernel-xen	3.0.101-108.165.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	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)

All national notices →

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 Free

CVSS 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 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&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✗ → ✓Sep 28, 2026, 10:08 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/07c176e7acc5579c133bb923ab21316d192d0a95

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records