Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-47669: nilfs2: fix state management in error path of log writing function

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.21% (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 036441e8438b29111fa75008f0ce305fb4e83c0a, 0a1a961bde4351dc047ffdeb2f1311ca16a700cc, 30562eff4a6dd35c4b5be9699ef61ad9f5f20a06.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 036441e8438b29111fa75008f0ce305fb4e83c0a, 0a1a961bde4351dc047ffdeb2f1311ca16a700cc, 30562eff4a6dd35c4b5be9699ef61ad9f5f20a06 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 state management in error path of log writing function After commit a694291a6211 ("nilfs2: separate wait function from nilfs_segctor_write") was applied, the log writing function nilfs_segctor_do_construct() was able to issue I/O requests continuously even if user data blocks were split into multiple logs across segments, but two potential flaws were introduced in its error handling. First, if nilfs_segctor_begin_construction() fails while creating the second or subsequent logs, the log writing function returns without calling nilfs_segctor_abort_construction(), so the writeback flag set on pages/folios will remain uncleared. This causes page cache operations to hang waiting for the writeback flag. For example, truncate_inode_pages_final(), which is called via nilfs_evict_inode() when an inode is evicted from memory, will hang. Second, the NILFS_I_COLLECTED flag set on normal inodes remain uncleared. As a result, if the next log write involves checkpoint creation, that's fine, but if a partial log write is performed that does not, inodes with NILFS_I_COLLECTED set are erroneously removed from the "sc_dirty_files" list, and their data and b-tree blocks may not be written to the device, corrupting the block mapping. Fix these issues by uniformly calling nilfs_segctor_abort_construction() on failure of each step in the loop in nilfs_segctor_do_construct(), having it clean up logs and segment usages according to progress, and correcting the conditions for calling nilfs_redirty_inodes() to ensure that the NILFS_I_COLLECTED flag is cleared.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Oct 9, 2024
Updated
Aug 5, 2026
EPSS
0.2% · 11th percentile
CWE
—

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.3
1.8 point gap

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/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-47669

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

Running WordPress? Scan your site free with WP Lens

  • 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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

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.33 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.33affected
    • a694291a6211537189c6080f77f63cdabfc9b63e and later · before 40a2757de2c376ef8a08d9ee9c81e77f3c750adfaffected · git
    • a694291a6211537189c6080f77f63cdabfc9b63e and later · before 036441e8438b29111fa75008f0ce305fb4e83c0aaffected · git
    • a694291a6211537189c6080f77f63cdabfc9b63e and later · before efdde00d4a1ef10bb71e09ebc67823a3d3ad725baffected · git
    • a694291a6211537189c6080f77f63cdabfc9b63e and later · before 3e349d7191f0688fc9808ef24fd4e4b4ef5ca876affected · git
    • a694291a6211537189c6080f77f63cdabfc9b63e and later · before 30562eff4a6dd35c4b5be9699ef61ad9f5f20a06affected · git
    • a694291a6211537189c6080f77f63cdabfc9b63e and later · before 0a1a961bde4351dc047ffdeb2f1311ca16a700ccaffected · git
    • a694291a6211537189c6080f77f63cdabfc9b63e and later · before 74866c16ea2183f52925fa5d76061a1fe7f7737baffected · git
    • a694291a6211537189c6080f77f63cdabfc9b63e and later · before 6576dd6695f2afca3f4954029ac4a64f82ba60abaffected · git
    • before 2.6.33not 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

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-47667Oct 9, 2024 · PCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0)
    22Monitor
  • ← EarlierCVE-2024-47668Oct 9, 2024 · lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc()
    18Monitor
  • Later →CVE-2024-47670Oct 9, 2024 · ocfs2: add bounds checking to ocfs2_xattr_find_entry()
    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 Linux036441e8438b29111fa75008f0ce305fb4e83c0aVendor (CNA)
Linux Linux0a1a961bde4351dc047ffdeb2f1311ca16a700ccVendor (CNA)
Linux Linux30562eff4a6dd35c4b5be9699ef61ad9f5f20a06Vendor (CNA)
Linux Linux3e349d7191f0688fc9808ef24fd4e4b4ef5ca876Vendor (CNA)
Linux Linux40a2757de2c376ef8a08d9ee9c81e77f3c750adfVendor (CNA)
Linux Linux6576dd6695f2afca3f4954029ac4a64f82ba60abVendor (CNA)
Linux Linux74866c16ea2183f52925fa5d76061a1fe7f7737bVendor (CNA)
Linux Linuxefdde00d4a1ef10bb71e09ebc67823a3d3ad725bVendor (CNA)
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.

Credits

All researchers

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)

—

CVSS vector

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

nvd-primary

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)

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

All records