Kernel memory corruption via unaligned KASAN region
Published Apr 3, 2024 · Updated Aug 5, 2026
Memory corruption in affected Linux kernel releases allows local users to overwrite kernel memory on PowerPC 32-bit KASAN systems. In kasan_init_region, an unaligned k_start makes block + k_cur - k_start point before the memblock_alloc allocation, so later reservations do not protect the aliased page. The flaw is established during boot only when 32-bit PowerPC KASAN is enabled; subsequent ordinary local kernel activity can corrupt unrelated kernel objects, disclose memory, or crash the system.
Summary
What happened
Memory corruption in affected Linux kernel releases allows local users to overwrite kernel memory on PowerPC 32-bit KASAN systems. In kasan_init_region, an unaligned k_start makes block + k_cur - k_start point before the memblock_alloc allocation, so later reservations do not protect the aliased page. The flaw is established during boot only when 32-bit PowerPC KASAN is enabled; subsequent ordinary local kernel activity can corrupt unrelated kernel objects, disclose memory, or crash the system.
The record
- CVE
- CVE-2024-26712
- Published
- Apr 3, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 3, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=5.3.6 <5.4
- Affected versionversion=5.4
- Affected versionversion=5ce93076d8ee2a0fac3ad4adbd2e91b6197146db
- Affected versionversion=663c0c9496a69f80011205ba3194049bcafd681d <0516c06b19dc64807c10e01bb99b552bdf2d7dbe
- Affected versionversion=663c0c9496a69f80011205ba3194049bcafd681d <0c09912dd8387e228afcc5e34ac5d79b1e3a1058
- Affected versionversion=663c0c9496a69f80011205ba3194049bcafd681d <230e89b5ad0a33f530a2a976b3e5e4385cb27882
- Affected versionversion=663c0c9496a69f80011205ba3194049bcafd681d <2738e0aa2fb24a7ab9c878d912dc2b239738c6c6
- Affected versionversion=663c0c9496a69f80011205ba3194049bcafd681d <4a7aee96200ad281a5cc4cf5c7a2e2a49d2b97b0
- Affected versionversion=663c0c9496a69f80011205ba3194049bcafd681d <70ef2ba1f4286b2b73675aeb424b590c92d57b25
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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