CVE-2025-39920
MediumIn the Linux kernel, the following vulnerability has been resolved: pcmcia: Add error handling for add_interval() in do_validate_mem() In the do_validate_mem(), the call to add_interval() does not handle errors. If kmalloc() fails in add_interval(), it could result in a null pointer being inserted into the linked list, leading to illegal memory access when sub_interval() is called next. This patch adds an error handling for the add_interval(). If add_interval() returns an error, the function will return early with the error code.
CVSS 3.1 score
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness type
CWE-476CVE-2025-39920 is a NULL Pointer Dereference vulnerability
What is NULL Pointer Dereference?
The product dereferences a pointer that it expects to be valid but is NULL, typically causing a crash. Learn more on MITRE CWE
Affected versions
Linux kernel versions
2.6.34
and later are affected. Fixed in
5.4.299,
5.10.243,
5.15.192,
6.1.151,
6.6.105,
6.12.46,
6.16.6,
6.17
and their respective stable series.
References
10 total-
Patch
-
Patch
-
Patch
-
Patch
-
Patch
Frequently asked questions
-
What is CVE-2025-39920?
CVE-2025-39920 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 , classified as a NULL Pointer Dereference flaw (CWE-476) . It affects Linux kernel versions from 2.6.34 onward and has been patched in 5.4.299, 5.10.243, 5.15.192 and others. CVE-2025-39920 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2025-39920?
CVE-2025-39920 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-2025-39920?
Yes. CVE-2025-39920 has been patched. Fixed versions include 5.4.299, 5.10.243, 5.15.192 and others. If you are running Linux kernel 2.6.34 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2025-39920 actively exploited?
No. CVE-2025-39920 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.