Kernel crash via oversized CPER firmware record
Published May 6, 2026 · Updated May 6, 2026
Out-of-bounds read in affected Linux Kernel releases allows local users to cause a kernel OOPS via malformed CPER firmware data. The APEI/GHES path validates the reported CPER length against the 64 KB GHES_ESTATUS_MAX_SIZE limit instead of the smaller page-backed allocation, then prints beyond that allocation. Reachability requires firmware-controlled CPER data and low local privileges; the demonstrated consequence is a kernel OOPS and service interruption, not data modification or disclosure.
Summary
What happened
Out-of-bounds read in affected Linux Kernel releases allows local users to cause a kernel OOPS via malformed CPER firmware data. The APEI/GHES path validates the reported CPER length against the 64 KB GHES_ESTATUS_MAX_SIZE limit instead of the smaller page-backed allocation, then prints beyond that allocation. Reachability requires firmware-controlled CPER data and low local privileges; the demonstrated consequence is a kernel OOPS and service interruption, not data modification or disclosure.
The record
- CVE
- CVE-2026-43277
- Published
- May 6, 2026
- Updated
- May 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 6, 2026CVE publishedPublication date reported by the CVE source.
- May 6, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <616c120dcdf1ce96edcd818e38bce49667f80689
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6f5d41984ad896736c23e2fff7c80e15c1319132
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <92ba79074c58e65a6e32713758c5a9aecd33c2ea
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <98bd9b28d4d11e6739ad86524b4be4ada9025e60
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b6be51a12441136fdf8c49b2525689fbea1856e1
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e0ec99115e135dbb58e11a0df007c7d4771d4a17
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f3740a1562445f36f08afab8af59e37117b3acdc
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fa2408a24f8f0db14d9cfc613ef162dc267d7ad4
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