NVD

CVE-2022-50487 Detail

Rejected

This CVE has been marked Rejected in the CVE List. These CVEs are stored in the NVD, but do not show up in search results by default.

Description

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

Metrics

NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed.

CVSS 4.0 Severity and Vector Strings:

NIST: NVD

N/A

NVD assessment not yet provided.

CVSS 3.x Severity and Vector Strings:

NIST: NVD

Base Score: N/A

NVD assessment not yet provided.

CVSS 2.0 Severity and Vector Strings:

National Institute of Standards and Technology

NIST: NVD

Base Score: N/A

NVD assessment not yet provided.

References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [email protected].

URL	Source(s)	Tag(s)

Weakness Enumeration

CWE-ID	CWE Name	Source

Change History

3 change records found show changes

CVE Modified by kernel.org 10/10/2025 12:15:50 PM

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 from kernel.org 10/04/2025 12:15:45 PM

Action	Type	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

Quick Info

CVE Dictionary Entry:
CVE-2022-50487
NVD Published Date:
10/04/2025
NVD Last Modified:
10/10/2025
Source:
kernel.org

You are viewing this page in an unauthorized frame window.

Information Technology Laboratory

National Vulnerability Database

National Vulnerability Database

CVE-2022-50487 Detail

Description

Metrics

References to Advisories, Solutions, and Tools

Weakness Enumeration

Change History

CVE Modified by kernel.org 10/10/2025 12:15:50 PM

CVE Rejected by kernel.org 10/10/2025 12:15:50 PM

New CVE Received from kernel.org 10/04/2025 12:15:45 PM

Quick Info