CVE-2026-43266

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 ]

Gravité et risque d'exploitation

CVE-2026-43266 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.16 %, ce qui la place devant 5.1 % des CVE référencées.

Que faire ?

• Vérifiez si Linux (versions <eae21beecb95a3b69ee5c38a659f774e171d730e, <=6.1.*, 2f74f09bce4f8d0236f20174a6daae63e10fe733, <=6.12.*, 0, 7.0, <25b290624b0e3d2f0f90238709ee0b6009b9fde8, 6.1.165, 6.12.75, <64eb63f573f497553e1a0c388bbcdd639e0f0704, <c80113dcfc807308f5ab33847fae77e07531aeb8, <=5.10.*, <=6.6.*, <=6.19.*, 4.13, <ca2aad8771aa9091bc9e42e7d546bd40b72ddcd4, <=6.18.*, <a68d22902a6916e10ee235fee609239004e129d0, 6.19.6, 6.6.128, <4.13, 5.10.252, 6.18.16, <=*, <be10c1bdf64a39832998f54900aa309b3917abcf, <=5.15.*, 5.15.202, <45766863baf899059e75595dd3cb1116467f2095) est présent sur votre parc.
• Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
• À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
• Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

• https://git.kernel.org/stable/c/c80113dcfc807308f5ab33847fae77e07531aeb8
• https://git.kernel.org/stable/c/ca2aad8771aa9091bc9e42e7d546bd40b72ddcd4
• https://git.kernel.org/stable/c/a68d22902a6916e10ee235fee609239004e129d0
• https://git.kernel.org/stable/c/64eb63f573f497553e1a0c388bbcdd639e0f0704
• https://git.kernel.org/stable/c/be10c1bdf64a39832998f54900aa309b3917abcf
• https://git.kernel.org/stable/c/25b290624b0e3d2f0f90238709ee0b6009b9fde8
• https://git.kernel.org/stable/c/45766863baf899059e75595dd3cb1116467f2095
• https://git.kernel.org/stable/c/eae21beecb95a3b69ee5c38a659f774e171d730e