What is CVE-2025-38447?

CVE-2025-38447 is a High severity Linux kernel vulnerability with a CVSS score of 7.1 out of 10, classified as a Out-of-bounds Read flaw (CWE-125), affecting Linux kernel versions from 6.15 onward and patched in 6.15.7 and 6.16. CVE-2025-38447 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2025-38447?

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

Is there a patch available for CVE-2025-38447?

Yes, CVE-2025-38447 has been patched. Fixed versions include 6.15.7 and 6.16. If you are running Linux kernel 6.15 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2025-38447 actively exploited?

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

What is Out-of-bounds Read (CWE-125)?

The product reads data past the end or before the beginning of the intended buffer. See MITRE CWE for full details: https://cwe.mitre.org/data/definitions/125.html

CVE-2025-38447

High

In the Linux kernel, the following vulnerability has been resolved: mm/rmap: fix potential out-of-bounds page table access during batched unmap As pointed out by David[1], the batched unmap logic in try_to_unmap_one() may read past the end of a PTE table when a large folio's PTE mappings are not fully contained within a single page table. While this scenario might be rare, an issue triggerable from userspace must be fixed regardless of its likelihood. This patch fixes the out-of-bounds access by refactoring the logic into a new helper, folio_unmap_pte_batch(). The new helper correctly calculates the safe batch size by capping the scan at both the VMA and PMD boundaries. To simplify the code, it also supports partial batching (i.e., any number of pages from 1 up to the calculated safe maximum), as there is no strong reason to special-case for fully mapped folios.

Package Linux Kernel

Published 2025-07-25

Last modified 2025-11-19

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

7.1

out of 10

High

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

High

Vector string

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

Weakness type

CWE-125

CVE-2025-38447 is a Out-of-bounds Read vulnerability

What is Out-of-bounds Read?

The product reads data past the end or before the beginning of the intended buffer. Learn more on MITRE CWE

Affected versions

Linux kernel versions 6.15 and later are affected. Fixed in 6.15.7, 6.16 and their respective stable series.

Affected from

≥ 6.15

Fixed in

✓ 6.15.7 6.15.x ✓ 6.16

References

2 total

Kernel Git
https://git.kernel.org/stable/c/510fe9c15d07e765d96be9a9dc37e5057c6c09f4

Patch
Kernel Git
https://git.kernel.org/stable/c/ddd05742b45b083975a0855ef6ebbf88cf1f532a

Patch

Details

CVE ID CVE-2025-38447

Severity High

CVSS score 7.1 / 10

CVSS version 3.1

Published 2025-07-25

Modified 2025-11-19

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2025-38447?

CVE-2025-38447 is a High severity Linux kernel vulnerability with a CVSS score of 7.1 out of 10 , classified as an Out-of-bounds Read flaw (CWE-125) . It affects Linux kernel versions from 6.15 onward and has been patched in 6.15.7 and 6.16. CVE-2025-38447 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2025-38447?

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

Yes. CVE-2025-38447 has been patched. Fixed versions include 6.15.7 and 6.16. If you are running Linux kernel 6.15 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2025-38447 actively exploited?

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