CVE-2026-43266None▾ SunlitIn 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…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.
Exploit-prediction probability, daily snapshots since Nov 6.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.1%
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 ]
Linux >= 2f74f09bce4f8d0236f20174a6daae63e10fe733 < c80113dcfc807308f5ab33847fae77e07531aeb8Linux >= 2f74f09bce4f8d0236f20174a6daae63e10fe733 < ca2aad8771aa9091bc9e42e7d546bd40b72ddcd4Linux >= 2f74f09bce4f8d0236f20174a6daae63e10fe733 < a68d22902a6916e10ee235fee609239004e129d0Linux >= 2f74f09bce4f8d0236f20174a6daae63e10fe733 < 64eb63f573f497553e1a0c388bbcdd639e0f0704Linux >= 2f74f09bce4f8d0236f20174a6daae63e10fe733 < be10c1bdf64a39832998f54900aa309b3917abcfLinux >= 2f74f09bce4f8d0236f20174a6daae63e10fe733 < 25b290624b0e3d2f0f90238709ee0b6009b9fde8Linux >= 2f74f09bce4f8d0236f20174a6daae63e10fe733 < 45766863baf899059e75595dd3cb1116467f2095Linux >= 2f74f09bce4f8d0236f20174a6daae63e10fe733 < eae21beecb95a3b69ee5c38a659f774e171d730eLinux 4.13Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99284Nonenet: skbuff: propagate shared-frag marker in skb_zerocopy()
CVE-2026-99283Nonenetfilter: conntrack: tcp: use UNACK timeout for non-closing RST packets
CVE-2026-99272Nonesmb: client: validate the data area in SMB2_read()
CVE-2026-99271NoneALSA: line6: Clear prev_fbuf on capture buffer release
CVE-2026-99273Noneksmbd: reserve space for the UTF-16 terminator in stream info
CVE-2026-99275Nonesmb: client: reject short SESSION_SETUP responses