Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-50229: nilfs2: fix potential deadlock with newly created symlinks

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.20% (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 1246d86e7bbde265761932c6e2dce28c69cdcb91, 4.5, 58c7f44c7b9e5ac7e3b1e5da2572ed7767a12f38; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1.

Low priority for now. Upgrade to Linux Linux 1246d86e7bbde265761932c6e2dce28c69cdcb91, 4.5, 58c7f44c7b9e5ac7e3b1e5da2572ed7767a12f38; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1 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 potential deadlock with newly created symlinks Syzbot reported that page_symlink(), called by nilfs_symlink(), triggers memory reclamation involving the filesystem layer, which can result in circular lock dependencies among the reader/writer semaphore nilfs->ns_segctor_sem, s_writers percpu_rwsem (intwrite) and the fs_reclaim pseudo lock. This is because after commit 21fc61c73c39 ("don't put symlink bodies in pagecache into highmem"), the gfp flags of the page cache for symbolic links are overwritten to GFP_KERNEL via inode_nohighmem(). This is not a problem for symlinks read from the backing device, because the __GFP_FS flag is dropped after inode_nohighmem() is called. However, when a new symlink is created with nilfs_symlink(), the gfp flags remain overwritten to GFP_KERNEL. Then, memory allocation called from page_symlink() etc. triggers memory reclamation including the FS layer, which may call nilfs_evict_inode() or nilfs_dirty_inode(). And these can cause a deadlock if they are called while nilfs->ns_segctor_sem is held: Fix this issue by dropping the __GFP_FS flag from the page cache GFP flags of newly created symlinks in the same way that nilfs_new_inode() and __nilfs_read_inode() do, as a workaround until we adopt nofs allocation scope consistently or improve the locking constraints.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Nov 9, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 10th 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.

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-50229

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 kernel4.5 and later · before 4.19.323
  • linux linux kernel4.20 and later · before 5.4.285
  • linux linux kernel5.5 and later · before 5.10.229
  • linux linux kernel5.11 and later · before 5.15.171
  • linux linux kernel5.16 and later · before 6.1.116
  • linux linux kernel6.2 and later · before 6.6.60
  • linux linux kernel6.7 and later · before 6.11.7
  • linux linux kernel4.4.116
  • linux linux kernel6.12

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

    • 076e4ab3279eb3ddb206de44d04df7aeb2428e09, 4.5affected
    • 21fc61c73c3903c4c312d0802da01ec2b323d174 and later · before cc38c596e648575ce58bfc31623a6506eda4b94aaffected · git
    • 21fc61c73c3903c4c312d0802da01ec2b323d174 and later · before a1686db1e59f8fc016c4c9361e2119dd206f479aaffected · git
    • 21fc61c73c3903c4c312d0802da01ec2b323d174 and later · before c72e0df0b56c1166736dc8eb62070ebb12591447affected · git
    • 21fc61c73c3903c4c312d0802da01ec2b323d174 and later · before 69548bb663fcb63f9ee0301be808a36b9d78dac3affected · git
    • 21fc61c73c3903c4c312d0802da01ec2b323d174 and later · before 58c7f44c7b9e5ac7e3b1e5da2572ed7767a12f38affected · git
    • 21fc61c73c3903c4c312d0802da01ec2b323d174 and later · before 1246d86e7bbde265761932c6e2dce28c69cdcb91affected · git
    • 21fc61c73c3903c4c312d0802da01ec2b323d174 and later · before 9aa5d43ac4cace8fb9bd964ff6c23f599dc3cd24affected · git
    • 21fc61c73c3903c4c312d0802da01ec2b323d174 and later · before b3a033e3ecd3471248d474ef263aadc0059e516aaffected · git
    • 4.4.116 and later · before 4.5affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.119-16.1.119-1
Debian:13linuxbefore 6.11.7-16.11.7-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-50225Nov 9, 2024 · btrfs: fix error propagation of split bios
    22Monitor
  • ← EarlierCVE-2024-50227Nov 9, 2024 · thunderbolt: Fix KASAN reported stack out-of-bounds read in tb_retimer_scan()
    28Monitor
  • Later →CVE-2024-50230Nov 9, 2024 · nilfs2: fix kernel bug due to missing clearing of checked flag
    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 Linux1246d86e7bbde265761932c6e2dce28c69cdcb91Vendor (CNA)
Linux Linux4.5Vendor (CNA)
Linux Linux58c7f44c7b9e5ac7e3b1e5da2572ed7767a12f38Vendor (CNA)
Linux Linux69548bb663fcb63f9ee0301be808a36b9d78dac3Vendor (CNA)
Linux Linux9aa5d43ac4cace8fb9bd964ff6c23f599dc3cd24Vendor (CNA)
Linux Linuxa1686db1e59f8fc016c4c9361e2119dd206f479aVendor (CNA)
Linux Linuxb3a033e3ecd3471248d474ef263aadc0059e516aVendor (CNA)
Linux Linuxc72e0df0b56c1166736dc8eb62070ebb12591447Vendor (CNA)
Linux Linuxcc38c596e648575ce58bfc31623a6506eda4b94aVendor (CNA)
azl3 kernel 6.6.57.1-7 on Azure Linux 3.06.6.64.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.64.2-1 on Azure Linux 3.06.6.64.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.167.1-2 on CBL Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.167.1-2 on CBL-Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.173.1-1 on CBL Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.119-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).

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-667 · Improper Locking

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.

Change log

  1. Fix✗ → ✓

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

References

Show all references (9 more)

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

All records