What is CVE-2024-35882?

CVE-2024-35882 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10, classified as a Memory Leak flaw (CWE-401), affecting Linux kernel versions from 6.6 onward and patched in 6.6.26, 6.8.5 and 6.9. CVE-2024-35882 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2024-35882?

CVE-2024-35882 has a CVSS score of 5.5 out of 10, rated Medium severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.

Is there a patch available for CVE-2024-35882?

Yes, CVE-2024-35882 has been patched. Fixed versions include 6.6.26, 6.8.5 and 6.9. If you are running Linux kernel 6.6 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2024-35882 actively exploited?

CVE-2024-35882 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is Memory Leak (CWE-401)?

The product does not release memory after use, causing gradual resource exhaustion. See MITRE CWE for full details: https://cwe.mitre.org/data/definitions/401.html

CVE-2024-35882

Medium

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.

Package Linux Kernel

Published 2024-05-19

Last modified 2025-03-05

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

5.5

out of 10

Medium

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

High

Vector string

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Weakness type

CWE-401

CVE-2024-35882 is a Memory Leak vulnerability

What is Memory Leak?

The product does not release memory after use, causing gradual resource exhaustion. Learn more on MITRE CWE

Affected versions

Linux kernel versions 6.6 and later are affected. Fixed in 6.6.26, 6.8.5, 6.9 and their respective stable series.

Affected from

≥ 6.6

Fixed in

✓ 6.6.26 6.6.x ✓ 6.8.5 6.8.x ✓ 6.9

References

3 total

Kernel Git
https://git.kernel.org/stable/c/05258a0a69b3c5d2c003f818702c0a52b6fea861

Mailing List Patch
Kernel Git
https://git.kernel.org/stable/c/1ba1291172f935e6b6fe703161a948f3347400b8

Mailing List Patch
Kernel Git
https://git.kernel.org/stable/c/a2ebedf7bcd17a1194a0a18122c885eb578ee882

Mailing List Patch

Details

CVE ID CVE-2024-35882

Severity Medium

CVSS score 5.5 / 10

CVSS version 3.1

Published 2024-05-19

Modified 2025-03-05

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2024-35882?

CVE-2024-35882 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 , classified as a Memory Leak flaw (CWE-401) . It affects Linux kernel versions from 6.6 onward and has been patched in 6.6.26, 6.8.5 and 6.9. CVE-2024-35882 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2024-35882?

CVE-2024-35882 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
Is there a patch available for CVE-2024-35882?

Yes. CVE-2024-35882 has been patched. Fixed versions include 6.6.26, 6.8.5 and 6.9. If you are running Linux kernel 6.6 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2024-35882 actively exploited?

No. CVE-2024-35882 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.