EFI/CPER: don't go past the ARM processor CPER record buffer
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 ]
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.252, 5.15.202, 6.1.165, 6.12.75, 6.18.16, 6.19.6, 6.6.128
- CVEs
- CVE-2026-43266
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 23:11 UTC · Revision 1
Source evidence
EFI/CPER: don't go past the ARM processor CPER record buffer
core-osv · Original sourcePublished 6 May 2026, 11:28 UTC
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 ]
osv:CVE-2026-43266
Kernel
Fixed versions: 5.10.252, 5.15.202, 6.1.165, 6.6.128, 6.12.75, 6.18.16, 6.19.6
Complete source record
{
"id": "2db92999ffb2132c73ff17b38731b27d8e3b1b70bbbe8fc75a1c9e0ea28d7576",
"url": "https://osv.dev/vulnerability/CVE-2026-43266",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "EFI/CPER: don't go past the ARM processor CPER record buffer",
"summary": "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 ]",
"evidence": "osv:CVE-2026-43266",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.252",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.202",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.165",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.128",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.75",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.16",
"evidence": "/affected/1/ranges"
},
{
"value": "6.19.6",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-43266",
"aliases": [
"CVE-2026-43266"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "2f74f09bce4f8d0236f20174a6daae63e10fe733"
},
{
"fixed": "c80113dcfc807308f5ab33847fae77e07531aeb8"
},
{
"fixed": "ca2aad8771aa9091bc9e42e7d546bd40b72ddcd4"
},
{
"fixed": "a68d22902a6916e10ee235fee609239004e129d0"
},
{
"fixed": "64eb63f573f497553e1a0c388bbcdd639e0f0704"
},
{
"fixed": "be10c1bdf64a39832998f54900aa309b3917abcf"
},
{
"fixed": "25b290624b0e3d2f0f90238709ee0b6009b9fde8"
},
{
"fixed": "45766863baf899059e75595dd3cb1116467f2095"
},
{
"fixed": "eae21beecb95a3b69ee5c38a659f774e171d730e"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-43266.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.13.0"
},
{
"fixed": "5.10.252"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.202"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.165"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.128"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.75"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.16"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "6.19.6"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-43266.json"
}
}
],
"modified": "2026-10-28T02:30:40.335555497Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/25b290624b0e3d2f0f90238709ee0b6009b9fde8",
"https://git.kernel.org/stable/c/45766863baf899059e75595dd3cb1116467f2095",
"https://git.kernel.org/stable/c/64eb63f573f497553e1a0c388bbcdd639e0f0704",
"https://git.kernel.org/stable/c/a68d22902a6916e10ee235fee609239004e129d0",
"https://git.kernel.org/stable/c/be10c1bdf64a39832998f54900aa309b3917abcf",
"https://git.kernel.org/stable/c/c80113dcfc807308f5ab33847fae77e07531aeb8",
"https://git.kernel.org/stable/c/ca2aad8771aa9091bc9e42e7d546bd40b72ddcd4",
"https://git.kernel.org/stable/c/eae21beecb95a3b69ee5c38a659f774e171d730e",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/43xxx/CVE-2026-43266.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-43266",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/43xxx/CVE-2026-43266.json"
}
},
"related_cves": [
{
"value": "CVE-2026-43266",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 507875,
"published_at": "2026-05-06T11:28:52.238+00:00"
}