CVE-2024-26678

x86/efistub: Use 1:1 file:memory mapping for PE/COFF .compat section

MEDIUM
5.5
CVSS Score
Published: April 2, 2024 at 07:01 AM UTC
Updated: June 17, 2026 at 07:18 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.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: x86/efistub: Use 1:1 file:memory mapping for PE/COFF .compat section The .compat section is a dummy PE section that contains the address of the 32-bit entrypoint of the 64-bit kernel image if it is bootable from 32-bit firmware (i.e., CONFIG_EFI_MIXED=y) This section is only 8 bytes in size and is only referenced from the loader, and so it is placed at the end of the memory view of the image, to avoid the need for padding it to 4k, which is required for sections appearing in the middle of the image. Unfortunately, this violates the PE/COFF spec, and even if most EFI loaders will work correctly (including the Tianocore reference implementation), PE loaders do exist that reject such images, on the basis that both the file and memory views of the file contents should be described by the section headers in a monotonically increasing manner without leaving any gaps. So reorganize the sections to avoid this issue. This results in a slight padding overhead (< 4k) which can be avoided if desired by disabling CONFIG_EFI_MIXED (which is only needed in rare cases these days)

Affected

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

6.7 ≤ v < 6.7.56.7 ≤ v < 6.83e3eabe26dc88692d34cf76ca0e0dd331481cc156.8 rc16.8 rc26.8 rc3686b58ce5052842bd34ea94870a2671317331716c4421279b6c278efe129bde7abc64af59ea2dfbd
Vendor states this is fixed in 0a962f2fbaa976af9eed21d0306370cded485787 (fixed)
Vendor states this is fixed in 1ad55cecf22f05f1c884adf63cc09d3c3e609ebf (fixed)
Vendor states this is fixed in 4adeeff8c12321cd453412a659c3c0eeb9bb2397 (fixed)
Vendor states this is fixed in d327e961573fc335af0ae8a160302205327e1f4e (fixed)
Vendor states this is fixed in 6.7 (unaffected)
Vendor states this is fixed in 6.7.5 (unaffected)
Vendor states this is fixed in 6.8 (unaffected)

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/0a962f2fbaa976af9eed21d0306370cded485787
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/1ad55cecf22f05f1c884adf63cc09d3c3e609ebf
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/4adeeff8c12321cd453412a659c3c0eeb9bb2397
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/d327e961573fc335af0ae8a160302205327e1f4e

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

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

Quick Info

StatusANALYZED
CWE
CWE-787

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