NVD / CVE Program· CNA Linux

CVE-2024-50043: nfsd: fix possible badness in FREE_STATEID

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.49% (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 6.7, 7ca9e472ce5c67daa3188a348ece8c02a0765039, c88c150a467fcb670a1608e2272beeee3e86df6e.
Severity is disputed: the assigning authority (CNA) scores it 9.8, NVD 7.8.

Low priority for now. Upgrade to Linux Linux 6.7, 7ca9e472ce5c67daa3188a348ece8c02a0765039, c88c150a467fcb670a1608e2272beeee3e86df6e 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: nfsd: fix possible badness in FREE_STATEID When multiple FREE_STATEIDs are sent for the same delegation stateid, it can lead to a possible either use-after-free or counter refcount underflow errors. In nfsd4_free_stateid() under the client lock we find a delegation stateid, however the code drops the lock before calling nfs4_put_stid(), that allows another FREE_STATE to find the stateid again. The first one will proceed to then free the stateid which leads to either use-after-free or decrementing already zeroed counter.

Memory safety

BDU:2025-07238

Published: Oct 21, 2024
Updated: Oct 21, 2026
EPSS: 0.4% · 42th 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.4%

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: 9.8; 2.0 point gap

CVSS:3.1/AV:N/AC:L/PR:N/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.

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
- 172d038b7c4d3cfa9fc5ac210577c5c4f8256320, 6.9affected
- 3f29cc82a84c23cfd12b903029dd26002ca825f5 and later · before 7ca9e472ce5c67daa3188a348ece8c02a0765039affected · git
- 3f29cc82a84c23cfd12b903029dd26002ca825f5 and later · before c88c150a467fcb670a1608e2272beeee3e86df6eaffected · git
- 6.6.160 and later · before 6.7affected · semver
- before 6.9not affected · semver
- 6.11.4 and later · up to and including 6.11.*not affected · semver
- 6.12 and laternot affected · original_commit_for_fix

Affected versions

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

linux linux kernel6.9 and later · before 6.11.4
linux linux kernel6.12

Package-level exposure

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

Ecosystem	Package	Affected range	Fix
Debian:13	linux	before 6.11.4-1	6.11.4-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-50039Oct 21, 2024 · net/sched: accept TCA_STAB only for root qdisc
22Monitor
← EarlierCVE-2024-50040Oct 21, 2024 · igb: Do not bring the device up after non-fatal error
22Monitor
Later →CVE-2024-50044Oct 21, 2024 · Bluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change
13Monitor

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	6.7	Vendor (CNA)
Linux Linux	7ca9e472ce5c67daa3188a348ece8c02a0765039	Vendor (CNA)
Linux Linux	c88c150a467fcb670a1608e2272beeee3e86df6e	Vendor (CNA)
debian:linux	6.11.4-1 · Debian:13	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.

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:11 PM UTC

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

References

git.kernel.org/stable/c/7ca9e472ce5c67daa3188a348ece8c02a0765039

Show all references (1 more)

git.kernel.org/stable/c/c88c150a467fcb670a1608e2272beeee3e86df6e

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

All records