CVE-2022-50401
BaseFortify
Publication date: 2025-09-18
Last updated on: 2025-12-11
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 4.4.229 (inc) to 4.5 (exc) |
| linux | linux_kernel | From 4.9.229 (inc) to 4.9.337 (exc) |
| linux | linux_kernel | From 4.14.186 (inc) to 4.14.303 (exc) |
| linux | linux_kernel | From 4.19.130 (inc) to 4.19.270 (exc) |
| linux | linux_kernel | From 5.4.49 (inc) to 5.4.229 (exc) |
| linux | linux_kernel | From 5.7.6 (inc) to 5.10.163 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.86 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.0.16 (exc) |
| linux | linux_kernel | From 6.1 (inc) to 6.1.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-415 | The product calls free() twice on the same memory address. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :
The impact of this vulnerability includes possible kernel instability such as crashes or memory corruption due to use-after-free errors. This can affect the availability and reliability of systems running the vulnerable Linux kernel with NFSv4.1 server enabled, potentially leading to denial of service or other unpredictable behavior.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring kernel logs for specific error messages related to the nfsd module, such as 'refcount_t: underflow; use-after-free' or warnings from refcount_warn_saturate. You can check the kernel log using commands like 'dmesg | grep refcount' or 'journalctl -k | grep nfsd' to identify these error messages indicating the vulnerability is triggered.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the Linux kernel to a version where this vulnerability is fixed, as the issue is resolved in the kernel by correcting the reference handling in nfsd under NFSv4.1. Until an update is applied, consider disabling or limiting NFSv4.1 services if possible to reduce exposure.
Can you explain this vulnerability to me?
This vulnerability is in the Linux kernel's NFS server (nfsd) implementation for NFSv4.1. It involves a double release (double svc_xprt_put) of a transport reference on an RPC creation failure. Specifically, when an error occurs, the code incorrectly gives a reference to the transport object that leads to it being released twice, causing a reference count underflow and use-after-free condition. This can lead to kernel warnings, potential crashes, or memory corruption.