0.0
NA
CVE-2022-50487
NFSD: Protect against send buffer overflow in NFSv3 READDIR
Description

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

INFO

Published Date :

Oct. 4, 2025, 4:15 p.m.

Last Modified :

Oct. 10, 2025, 4:15 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2022-50487 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
Solution
Update the Linux kernel to fix an NFSv3 READDIR vulnerability causing buffer overflow.
  • Update the Linux kernel to the latest version.
  • Apply security patches provided by your Linux distribution.
  • Restart NFS services after updating.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2022-50487 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2022-50487 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • CVE Rejected by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Oct. 10, 2025

    Action Type Old Value New Value
  • CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Oct. 10, 2025

    Action Type Old Value New Value
    Changed Description In the Linux kernel, the following vulnerability has been resolved: NFSD: Protect against send buffer overflow in NFSv3 READDIR Since before the git era, NFSD has conserved the number of pages held by each nfsd thread by combining the RPC receive and send buffers into a single array of pages. This works because there are no cases where an operation needs a large RPC Call message and a large RPC Reply message at the same time. Once an RPC Call has been received, svc_process() updates svc_rqst::rq_res to describe the part of rq_pages that can be used for constructing the Reply. This means that the send buffer (rq_res) shrinks when the received RPC record containing the RPC Call is large. A client can force this shrinkage on TCP by sending a correctly- formed RPC Call header contained in an RPC record that is excessively large. The full maximum payload size cannot be constructed in that case. Thanks to Aleksi Illikainen and Kari Hulkko for uncovering this issue. Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
    Removed Reference kernel.org: https://git.kernel.org/stable/c/071a076fd1b763aa6fe478efa047e0a549ba9c22
    Removed Reference kernel.org: https://git.kernel.org/stable/c/279274e31270c28b86feffe5e166d4088f22317b
    Removed Reference kernel.org: https://git.kernel.org/stable/c/57774b1526163766403167b7bf00b136fb103761
    Removed Reference kernel.org: https://git.kernel.org/stable/c/640f87c190e0d1b2a0fcb2ecf6d2cd53b1c41991
    Removed Reference kernel.org: https://git.kernel.org/stable/c/9c3224826ec17f14e8bdfc86cb7e82fe52d744a7
  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Oct. 04, 2025

    Action Type Old Value New Value
    Added Description In the Linux kernel, the following vulnerability has been resolved: NFSD: Protect against send buffer overflow in NFSv3 READDIR Since before the git era, NFSD has conserved the number of pages held by each nfsd thread by combining the RPC receive and send buffers into a single array of pages. This works because there are no cases where an operation needs a large RPC Call message and a large RPC Reply message at the same time. Once an RPC Call has been received, svc_process() updates svc_rqst::rq_res to describe the part of rq_pages that can be used for constructing the Reply. This means that the send buffer (rq_res) shrinks when the received RPC record containing the RPC Call is large. A client can force this shrinkage on TCP by sending a correctly- formed RPC Call header contained in an RPC record that is excessively large. The full maximum payload size cannot be constructed in that case. Thanks to Aleksi Illikainen and Kari Hulkko for uncovering this issue.
    Added Reference https://git.kernel.org/stable/c/071a076fd1b763aa6fe478efa047e0a549ba9c22
    Added Reference https://git.kernel.org/stable/c/279274e31270c28b86feffe5e166d4088f22317b
    Added Reference https://git.kernel.org/stable/c/57774b1526163766403167b7bf00b136fb103761
    Added Reference https://git.kernel.org/stable/c/640f87c190e0d1b2a0fcb2ecf6d2cd53b1c41991
    Added Reference https://git.kernel.org/stable/c/9c3224826ec17f14e8bdfc86cb7e82fe52d744a7
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
No CVSS metrics available for this vulnerability.