CVE-2022-50861
Description
In the Linux kernel, the following vulnerability has been resolved:
NFSD: Finish converting the NFSv2 GETACL result encoder
The xdr_stream conversion inadvertently left some code that set the page_len of the send buffer. The XDR stream encoders should handle this automatically now.
This oversight adds garbage past the end of the Reply message. Clients typically ignore the garbage, but NFSD does not need to send it, as it leaks stale memory contents onto the wire.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A memory leak in the NFSv2 GETACL result encoder causes stale kernel data to be appended to NFS Reply messages over the wire.
What the vulnerability is
In the Linux kernel, the NFSv2 GETACL result encoder was not fully converted to the xdr_stream interface, leaving a remnant that set the page_len of the send buffer [1][2]. The XDR stream encoders are supposed to handle this automatically, but this oversight resulted in garbage data being appended past the end of the NFS Reply message [1][2].
How it's exploited
An NFS client issuing a GETACL request to an NFSD server running an affected kernel would receive a Reply that contains the intended ACL data followed by extra bytes of stale kernel heap memory [1][2]. No authentication or special network position is required beyond the ability to send NFSv2 GETACL requests and receive the corresponding responses.
Impact
This flaw leaks stale memory contents onto the network wire. While many clients may ignore the trailing garbage, an adversary positioned between the server and client (or able to capture the network traffic) could retrieve fragments of kernel memory, potentially exposing sensitive information such as encryption keys, file data, or other privileged kernel state [1][2].
Mitigation
The fix was committed to the Linux kernel stable tree, converting the encoder completely to xdr_stream and removing the stale page_len assignment [1][2]. System administrators should apply the corresponding kernel update to stop the memory leak. No workaround is available; upgrading the kernel is the only mitigation.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
5a20b0abab9665030d4d2bf8bd5b867fd2d7f2b825efb0577ea5021e911d3Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
5- git.kernel.org/stable/c/2b825efb0577a32a872e872a869e0947cf9dd6d3nvd
- git.kernel.org/stable/c/5030d4d2bf8b6f6f3d16401ab92a88bc5aa2377anvd
- git.kernel.org/stable/c/a20b0abab966a189a79aba6ebf41f59024a3224dnvd
- git.kernel.org/stable/c/d5b867fd2d7f79630b1a2906a7bb4f4b75bf297anvd
- git.kernel.org/stable/c/ea5021e911d3479346a75ac9b7d9dcd751b0fb99nvd
News mentions
0No linked articles in our index yet.