Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-46781: nilfs2: fix missing cleanup on rollforward recovery error

Noroxi assessment

Priority: Monitor (action score 22/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.25% (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 07e4dc2fe000ab008bcfe90be4324ef56b5b4355, 1cf1f7e8cd47244fa947d357ef1f642d91e219a3, 35a9a7a7d94662146396199b0cfd95f9517cdd14; Azure Linux 3.0 ARM 6.6.51.1-5; Azure Linux 3.0 x64 6.6.51.1-5.
  • Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 07e4dc2fe000ab008bcfe90be4324ef56b5b4355, 1cf1f7e8cd47244fa947d357ef1f642d91e219a3, 35a9a7a7d94662146396199b0cfd95f9517cdd14; Azure Linux 3.0 ARM 6.6.51.1-5; Azure Linux 3.0 x64 6.6.51.1-5 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 missing cleanup on rollforward recovery error In an error injection test of a routine for mount-time recovery, KASAN found a use-after-free bug. It turned out that if data recovery was performed using partial logs created by dsync writes, but an error occurred before starting the log writer to create a recovered checkpoint, the inodes whose data had been recovered were left in the ns_dirty_files list of the nilfs object and were not freed. Fix this issue by cleaning up inodes that have read the recovery data if the recovery routine fails midway before the log writer starts.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Sep 18, 2024
Updated
Aug 5, 2026
EPSS
0.2% · 16th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 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
5.5
CNA · Linux
7.8
2.3 point gap

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

Follow CVE-2024-46781

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

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.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel2.6.30 and later · before 4.19.322
  • linux linux kernel4.20 and later · before 5.4.284
  • linux linux kernel5.5 and later · before 5.10.226
  • linux linux kernel5.11 and later · before 5.15.167
  • linux linux kernel5.16 and later · before 6.1.110
  • linux linux kernel6.2 and later · before 6.6.51
  • linux linux kernel6.7 and later · before 6.10.10
  • linux linux kernel6.11

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
    • 0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b and later · before 35a9a7a7d94662146396199b0cfd95f9517cdd14affected · git
    • 0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b and later · before da02f9eb333333b2e4f25d2a14967cff785ac82eaffected · git
    • 0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b and later · before 07e4dc2fe000ab008bcfe90be4324ef56b5b4355affected · git
    • 0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b and later · before 8e2d1e9d93c4ec51354229361ac3373058529ec4affected · git
    • 0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b and later · before ca92c4bff2833cb30d493b935168d6cccd5c805daffected · git
    • 0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b and later · before 9d8c3a585d564d776ee60d4aabec59b404be7403affected · git
    • 0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b and later · before 1cf1f7e8cd47244fa947d357ef1f642d91e219a3affected · git
    • 0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b and later · before 5787fcaab9eb5930f5378d6a1dd03d916d146622affected · git
    • before 2.6.30not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.112-16.1.112-1
Debian:13linuxbefore 6.10.11-16.10.11-1

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-46779Sep 18, 2024 · drm/imagination: Free pvr_vm_gpuva after unlink
    22Monitor
  • ← EarlierCVE-2024-46780Sep 18, 2024 · nilfs2: protect references to superblock parameters exposed in sysfs
    22Monitor
  • Later →CVE-2024-46782Sep 18, 2024 · ila: call nf_unregister_net_hooks() sooner
    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 / packageFixed versionSource
Linux Linux07e4dc2fe000ab008bcfe90be4324ef56b5b4355Vendor (CNA)
Linux Linux1cf1f7e8cd47244fa947d357ef1f642d91e219a3Vendor (CNA)
Linux Linux35a9a7a7d94662146396199b0cfd95f9517cdd14Vendor (CNA)
Linux Linux5787fcaab9eb5930f5378d6a1dd03d916d146622Vendor (CNA)
Linux Linux8e2d1e9d93c4ec51354229361ac3373058529ec4Vendor (CNA)
Linux Linux9d8c3a585d564d776ee60d4aabec59b404be7403Vendor (CNA)
Linux Linuxca92c4bff2833cb30d493b935168d6cccd5c805dVendor (CNA)
Linux Linuxda02f9eb333333b2e4f25d2a14967cff785ac82eVendor (CNA)
Azure Linux 3.0 ARM6.6.51.1-5 · kernelMicrosoft (MSRC)
Azure Linux 3.0 x646.6.51.1-5 · kernelMicrosoft (MSRC)
CBL Mariner 2.0 ARM5.15.167.1-1 · kernelMicrosoft (MSRC)
CBL Mariner 2.0 x645.15.167.1-1 · kernelMicrosoft (MSRC)
debian:linux6.1.112-1 · Debian:12Package 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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
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:N/I:N/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.

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

Vulnerable

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

Fixed

c
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

All records