CVE-2026-43266: EFI/CPER: don't go past the ARM processor CPER record buffer
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.11% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 25b290624b0e3d2f0f90238709ee0b6009b9fde8, 45766863baf899059e75595dd3cb1116467f2095, 64eb63f573f497553e1a0c388bbcdd639e0f0704.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 25b290624b0e3d2f0f90238709ee0b6009b9fde8, 45766863baf899059e75595dd3cb1116467f2095, 64eb63f573f497553e1a0c388bbcdd639e0f0704 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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 ]
- Published
- May 6, 2026
- Updated
- Nov 11, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- —
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.13affected
- 2f74f09bce4f8d0236f20174a6daae63e10fe733 and later · before c80113dcfc807308f5ab33847fae77e07531aeb8affected · git
- 2f74f09bce4f8d0236f20174a6daae63e10fe733 and later · before ca2aad8771aa9091bc9e42e7d546bd40b72ddcd4affected · git
- 2f74f09bce4f8d0236f20174a6daae63e10fe733 and later · before a68d22902a6916e10ee235fee609239004e129d0affected · git
- 2f74f09bce4f8d0236f20174a6daae63e10fe733 and later · before 64eb63f573f497553e1a0c388bbcdd639e0f0704affected · git
- 2f74f09bce4f8d0236f20174a6daae63e10fe733 and later · before be10c1bdf64a39832998f54900aa309b3917abcfaffected · git
- 2f74f09bce4f8d0236f20174a6daae63e10fe733 and later · before 25b290624b0e3d2f0f90238709ee0b6009b9fde8affected · git
- 2f74f09bce4f8d0236f20174a6daae63e10fe733 and later · before 45766863baf899059e75595dd3cb1116467f2095affected · git
- 2f74f09bce4f8d0236f20174a6daae63e10fe733 and later · before eae21beecb95a3b69ee5c38a659f774e171d730eaffected · git
- before 4.13not affected · semver
Affected versions · NVD (7)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.13 and later · before 5.10.252
- linux linux kernel5.11 and later · before 5.15.202
- linux linux kernel5.16 and later · before 6.1.165
- linux linux kernel6.2 and later · before 6.6.128
- linux linux kernel6.7 and later · before 6.12.75
- linux linux kernel6.13 and later · before 6.18.16
- linux linux kernel6.19 and later · before 6.19.6
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.170-1 | 6.1.170-1 |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.6-1 | 6.19.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-43264May 6, 2026 · fbdev: of: display_timing: fix refcount leak in of_get_display_timings()22Monitor
- ← EarlierCVE-2026-43265May 6, 2026 · KVM: x86: Ignore -EBUSY when checking nested events from vcpu_block()22Monitor
- Later →CVE-2026-43267May 6, 2026 · wifi: rtw89: fix potential zero beacon interval in beacon tracking22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 25b290624b0e3d2f0f90238709ee0b6009b9fde8 | Vendor (CNA) |
| Linux Linux | 45766863baf899059e75595dd3cb1116467f2095 | Vendor (CNA) |
| Linux Linux | 64eb63f573f497553e1a0c388bbcdd639e0f0704 | Vendor (CNA) |
| Linux Linux | a68d22902a6916e10ee235fee609239004e129d0 | Vendor (CNA) |
| Linux Linux | be10c1bdf64a39832998f54900aa309b3917abcf | Vendor (CNA) |
| Linux Linux | c80113dcfc807308f5ab33847fae77e07531aeb8 | Vendor (CNA) |
| Linux Linux | ca2aad8771aa9091bc9e42e7d546bd40b72ddcd4 | Vendor (CNA) |
| Linux Linux | eae21beecb95a3b69ee5c38a659f774e171d730e | Vendor (CNA) |
| debian:linux | 6.1.170-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0213 · May 12, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/45766863baf899059e75595dd3cb1116467f2095
- git.kernel.org/stable/c/64eb63f573f497553e1a0c388bbcdd639e0f0704
- git.kernel.org/stable/c/a68d22902a6916e10ee235fee609239004e129d0
- git.kernel.org/stable/c/be10c1bdf64a39832998f54900aa309b3917abcf
- git.kernel.org/stable/c/c80113dcfc807308f5ab33847fae77e07531aeb8
- git.kernel.org/stable/c/ca2aad8771aa9091bc9e42e7d546bd40b72ddcd4
- git.kernel.org/stable/c/eae21beecb95a3b69ee5c38a659f774e171d730e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.