Kernel memory corruption via misclassified text mapping
Published Mar 12, 2025 · Updated May 11, 2026
Out-of-bounds write in Linux kernel 4.13 through 6.14-rc3 allows local users to corrupt kernel memory through PowerPC text patching. text_area_cpu_up marks a directly mapped virtual area as VM_ALLOC, so KASAN leaves it poisoned because __vmalloc_node_range never initializes it before copy_to_kernel_nofault writes. The observed failure requires a KASAN-enabled PowerPC kernel and a path that compiles a seccomp BPF program, with impact limited to kernel availability.
Summary
What happened
Out-of-bounds write in Linux kernel 4.13 through 6.14-rc3 allows local users to corrupt kernel memory through PowerPC text patching. text_area_cpu_up marks a directly mapped virtual area as VM_ALLOC, so KASAN leaves it poisoned because __vmalloc_node_range never initializes it before copy_to_kernel_nofault writes. The observed failure requires a KASAN-enabled PowerPC kernel and a path that compiles a seccomp BPF program, with impact limited to kernel availability.
The record
- CVE
- CVE-2025-21866
- Published
- Mar 12, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-770, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 12, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=37bc3e5fd764fb258ff4fcbb90b6d1b67fb466c1 <2d542f13d26344e3452eee77613026ce9b653065
- Affected versionversion=37bc3e5fd764fb258ff4fcbb90b6d1b67fb466c1 <2e6c80423f201405fd65254e52decd21663896f3
- Affected versionversion=37bc3e5fd764fb258ff4fcbb90b6d1b67fb466c1 <6847b3e40bb963e57b61d1cc6fe84cb37b9d3d4c
- Affected versionversion=37bc3e5fd764fb258ff4fcbb90b6d1b67fb466c1 <8d06e9208184b2851fa79a3a39d6860320c8bdf8
- Affected versionversion=37bc3e5fd764fb258ff4fcbb90b6d1b67fb466c1 <97de5852058a299ba447cd9782fe96488d30108b
- Affected versionversion=37bc3e5fd764fb258ff4fcbb90b6d1b67fb466c1 <c905a3053518212a1017e50bd2be3bee59305bb0
- Affected versionversion=37bc3e5fd764fb258ff4fcbb90b6d1b67fb466c1 <d262a192d38e527faa5984629aabda2e0d1c4f54
- Affected versionversion=37bc3e5fd764fb258ff4fcbb90b6d1b67fb466c1 <f8d4c5b653c1bc0df56e15658bbf64fc359adc4e
- Affected versionversion=4.13
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo