Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-35882: Vulnerability in Linux Linux

0
Medium
VulnerabilityCVE-2024-35882cvecve-2024-35882
Published: Sun May 19 2024 (05/19/2024, 08:34:39 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

In the Linux kernel, the following vulnerability has been resolved: SUNRPC: Fix a slow server-side memory leak with RPC-over-TCP Jan Schunk reports that his small NFS servers suffer from memory exhaustion after just a few days. A bisect shows that commit e18e157bb5c8 ("SUNRPC: Send RPC message on TCP with a single sock_sendmsg() call") is the first bad commit. That commit assumed that sock_sendmsg() releases all the pages in the underlying bio_vec array, but the reality is that it doesn't. svc_xprt_release() releases the rqst's response pages, but the record marker page fragment isn't one of those, so it is never released. This is a narrow fix that can be applied to stable kernels. A more extensive fix is in the works.

AI-Powered Analysis

AILast updated: 06/29/2025, 16:57:54 UTC

Technical Analysis

CVE-2024-35882 is a vulnerability identified in the Linux kernel's SUNRPC subsystem, specifically affecting the handling of RPC-over-TCP communications. The issue arises from a memory leak on the server side of small NFS (Network File System) servers. The root cause is linked to a kernel commit (e18e157bb5c8) that changed the way RPC messages are sent over TCP, using a single sock_sendmsg() call. This commit incorrectly assumed that sock_sendmsg() would release all memory pages associated with the underlying bio_vec array. However, it does not release the record marker page fragment, which is part of the RPC message but not accounted for in the usual release process. As a result, this fragment remains allocated, causing a slow but persistent memory leak. Over time, this leak can lead to memory exhaustion on affected servers, particularly those running small NFS services, potentially causing degraded performance or service outages. The fix involves explicitly releasing the record marker page fragment to prevent the leak. This fix is narrow and applicable to stable kernel versions, with a more comprehensive fix planned. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet.

Potential Impact

For European organizations, especially those relying on Linux-based NFS servers for file sharing and storage services, this vulnerability poses a risk of resource exhaustion leading to denial of service conditions. Memory leaks, while not directly exploitable for code execution or privilege escalation, can degrade system stability and availability over time. This can impact critical infrastructure, enterprise file servers, and cloud services that depend on Linux kernel SUNRPC functionality. Organizations with smaller NFS deployments or embedded Linux devices acting as NFS servers are particularly vulnerable, as these systems may have limited memory resources and less frequent maintenance cycles. The gradual nature of the leak means the impact might not be immediately apparent, complicating detection and response. In sectors such as finance, manufacturing, and government within Europe, where Linux servers are prevalent, prolonged outages or degraded performance could disrupt operations and data availability.

Mitigation Recommendations

European organizations should prioritize patching affected Linux kernel versions as soon as updates become available from their Linux distribution vendors. Since the fix is narrow and applicable to stable kernels, applying these patches promptly will prevent the memory leak from occurring. In the interim, monitoring memory usage on NFS servers running RPC-over-TCP is critical to detect abnormal growth indicative of the leak. Implementing automated alerts for unusual memory consumption can help trigger timely investigation and remediation. Organizations should also review their NFS server configurations to assess whether RPC-over-TCP is necessary or if alternative protocols or configurations can reduce exposure. For embedded or less frequently updated systems, consider scheduled reboots or memory cleanup procedures to mitigate the slow leak until patches are applied. Additionally, maintaining robust backup and recovery processes will help minimize operational impact if service degradation occurs.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2024-05-17T13:50:33.112Z
Cisa Enriched
true
Cvss Version
null
State
PUBLISHED

Threat ID: 682d982ac4522896dcbe375f

Added to database: 5/21/2025, 9:08:58 AM

Last enriched: 6/29/2025, 4:57:54 PM

Last updated: 12/2/2025, 10:10:50 PM

Views: 37

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats