cve.bz

CVE-2024-50043 linux linux kernel: Use After Free

7.8 highEPSS 0.5%Fix available

High (7.8) in linux linux kernel. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 43rd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2024-10-22. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-416 Use After Free
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-50043 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-50043?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-50043?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-50043 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2024-50043

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2024-50043](https://cve.bz/cve/badge/CVE-2024-50043.svg)](https://cve.bz/cve/CVE-2024-50043)

HTML:

<a href="https://cve.bz/cve/CVE-2024-50043"><img src="https://cve.bz/cve/badge/CVE-2024-50043.svg" alt="CVE-2024-50043"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linuxfrom 6.6.160 before 6.7
Linux6.9 and later

Fixed in

ProductRelease lineFixed in
Linux6.116.11.4
Linuxlater releases6.12

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13, 14linux6.11.4-1DEBIAN-CVE-2024-50043
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2024-50043
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 11 moreno fix listedUBUNTU-CVE-2024-50043
Ubuntu20.04:LTSlinux-gke, linux-riscv, linux-raspi2 and 24 moreno fix listedUBUNTU-CVE-2024-50043
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2024-50043
Ubuntu24.04:LTSlinux-oem-6.116.11.0-1015.15UBUNTU-CVE-2024-50043 USN-7310-1
Ubuntu24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2024-50043
openSUSETumbleweedkernel-source6.11.8-1.1openSUSE-SU-2024:14500-1
openSUSETumbleweedkernel-source-longterm6.12.11-1.1openSUSE-SU-2025:14705-1
Alpaquita25, streamlinux-lts6.12.41-r0BELL-CVE-2024-50043

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's mitigation

To mitigate this vulnerability, restrict network access to the NFS service to only trusted clients or networks. This can be achieved by configuring firewall rules.

For systems using `firewalld`:

`firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="<TRUSTED_NETWORK>" port port="2049" protocol="tcp" accept'`

`firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="<TRUSTED_NETWORK>" port port="2049" protocol="udp" accept'`

`firewall-cmd --reload`

Replace `<TRUSTED_NETWORK>` with the IP address or network range of your trusted NFS clients. This action may impact legitimate NFS clients if not configured correctly. Reloading the firewall service is required for changes to take effect.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelOut of support scope
Red Hat Enterprise Linux 7kernel-rtOut of support scope
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2024-50043.

References

Check your stackJSON