CVE-2024-53173: NFSv4.0: Fix a use-after-free problem in the asynchronous open()
In the Linux kernel, the following vulnerability has been resolved:
NFSv4.0: Fix a use-after-free problem in the asynchronous open()
Yang Erkun reports that when two threads are opening files at the same time, and are forced to abort before a reply is seen, then the call to nfsreleaseseqid() in nfs4opendatafree() can result in a use-after-free of the pointer to the defunct rpc task of the other thread. The fix is to ensure that if the RPC call is aborted before the call to nfswaitonsequence() is complete, then we must call nfsreleaseseqid() in nfs4openrelease() before the rpctask is freed.
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1 - Upgrade
Upgrade
debian/linux-6.1to a version that resolves this vulnerability.Fixed in 6.1.129-1~deb11u1
Event History
Frequently Asked Questions
What is the severity of CVE-2024-53173?
The severity of CVE-2024-53173 is rated as high due to the potential for arbitrary memory access leading to system instability.
How do I fix CVE-2024-53173?
To fix CVE-2024-53173, it is recommended to upgrade your Linux kernel to a version that has the patch applied, specifically beyond the affected versions.
What type of systems are affected by CVE-2024-53173?
CVE-2024-53173 affects Linux kernel versions ranging from 2.6.16 up to 6.12.2 based on specific version ranges.
What are the risks of not addressing CVE-2024-53173?
Failing to address CVE-2024-53173 may expose systems to potential exploitation, leading to data corruption, crashes, or unauthorized access.
Who reported the vulnerability CVE-2024-53173?
CVE-2024-53173 was reported by Yang Erkun, highlighting a use-after-free issue in the asynchronous open function of NFSv4.0.