CVE-2026-43266

EFI/CPER: don't go past the ARM processor CPER record buffer

MEDIUM
5.5
CVSS Score
Published: May 6, 2026 at 11:28 AM UTC
Updated: June 17, 2026 at 10:49 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.1%

Description

In the Linux kernel, the following vulnerability has been resolved: EFI/CPER: don't go past the ARM processor CPER record buffer There's a logic inside GHES/CPER to detect if the section_length is too small, but it doesn't detect if it is too big. Currently, if the firmware receives an ARM processor CPER record stating that a section length is big, kernel will blindly trust section_length, producing a very long dump. For instance, a 67 bytes record with ERR_INFO_NUM set 46198 and section length set to 854918320 would dump a lot of data going a way past the firmware memory-mapped area. Fix it by adding a logic to prevent it to go past the buffer if ERR_INFO_NUM is too big, making it report instead: [Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [Hardware Error]: event severity: recoverable [Hardware Error]: Error 0, type: recoverable [Hardware Error]: section_type: ARM processor error [Hardware Error]: MIDR: 0xff304b2f8476870a [Hardware Error]: section length: 854918320, CPER size: 67 [Hardware Error]: section length is too big [Hardware Error]: firmware-generated error record is incorrect [Hardware Error]: ERR_INFO_NUM is 46198 [ rjw: Subject and changelog tweaks ]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.13 ≤ v < 5.10.2524.13 ≤ v < 5.15.2024.13 ≤ v < 6.1.1654.13 ≤ v < 6.12.754.13 ≤ v < 6.18.164.13 ≤ v < 6.19.64.13 ≤ v < 6.6.1284.13 ≤ v < 7.05.11 ≤ v < 5.15.2025.16 ≤ v < 6.1.1656.13 ≤ v < 6.18.166.19 ≤ v < 6.19.66.2 ≤ v < 6.6.1286.7 ≤ v < 6.12.752f74f09bce4f8d0236f20174a6daae63e10fe7334.13
Vendor states this is fixed in 25b290624b0e3d2f0f90238709ee0b6009b9fde8 (fixed)
Vendor states this is fixed in 45766863baf899059e75595dd3cb1116467f2095 (fixed)
Vendor states this is fixed in 64eb63f573f497553e1a0c388bbcdd639e0f0704 (fixed)
Vendor states this is fixed in a68d22902a6916e10ee235fee609239004e129d0 (fixed)
Vendor states this is fixed in be10c1bdf64a39832998f54900aa309b3917abcf (fixed)
Vendor states this is fixed in c80113dcfc807308f5ab33847fae77e07531aeb8 (fixed)
Vendor states this is fixed in ca2aad8771aa9091bc9e42e7d546bd40b72ddcd4 (fixed)
Vendor states this is fixed in eae21beecb95a3b69ee5c38a659f774e171d730e (fixed)
Vendor states this is fixed in 4.13 (unaffected)
Vendor states this is fixed in 5.10.252 (unaffected)
Vendor states this is fixed in 5.15.202 (unaffected)
Vendor states this is fixed in 6.1.165 (unaffected)
Vendor states this is fixed in 6.12.75 (unaffected)
Vendor states this is fixed in 6.18.16 (unaffected)
Vendor states this is fixed in 6.19.6 (unaffected)
Vendor states this is fixed in 6.6.128 (unaffected)
Vendor states this is fixed in 7.0 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card