CVE-2024-26678
published 2024-04-02CVE-2024-26678: 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…
PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.22%
13.2th percentile
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
10 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.7.7-1 (forky) | linux 6.7.7-1 (forky) |
| linux | linux | — | — |
| linux | linux | >= 3e3eabe26dc88692d34cf76ca0e0dd331481cc15 < 4adeeff8c12321cd453412a659c3c0eeb9bb2397 | 4adeeff8c12321cd453412a659c3c0eeb9bb2397 |
| linux | linux | >= 3e3eabe26dc88692d34cf76ca0e0dd331481cc15 < 1ad55cecf22f05f1c884adf63cc09d3c3e609ebf | 1ad55cecf22f05f1c884adf63cc09d3c3e609ebf |
| linux | linux | >= 686b58ce5052842bd34ea94870a2671317331716 < 0a962f2fbaa976af9eed21d0306370cded485787 | 0a962f2fbaa976af9eed21d0306370cded485787 |
| linux | linux | >= c4421279b6c278efe129bde7abc64af59ea2dfbd < d327e961573fc335af0ae8a160302205327e1f4e | d327e961573fc335af0ae8a160302205327e1f4e |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 6.7.7-1 | 6.7.7-1 |
| linux | linux_kernel | >= 0 < 6.7.7-1 | 6.7.7-1 |
| linux | linux_kernel | >= 6.7 < 6.7.5 | 6.7.5 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5LOW
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: x86/efistub: Use 1:1 file:memory mapping for PE/COFF .compat section
vendor_redhat·2024-04-02·CVSS 5.5
CVE-2024-26678 [MEDIUM] CWE-20 kernel: x86/efistub: Use 1:1 file:memory mapping for PE/COFF .compat section
kernel: x86/efistub: Use 1:1 file:memory mapping for PE/COFF .compat section
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), P
Debian
CVE-2024-26678: linux - In the Linux kernel, the following vulnerability has been resolved: x86/efistub...
vendor_debian·2024·CVSS 5.5
CVE-2024-26678 [MEDIUM] CVE-2024-26678: linux - In the Linux kernel, the following vulnerability has been resolved: x86/efistub...
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 an
OSV
CVE-2024-26678: In the Linux kernel, the following vulnerability has been resolved: x86/efistub: Use 1:1 file:memory mapping for PE/COFF
osv·2024-04-02·CVSS 5.5
CVE-2024-26678 [MEDIUM] CVE-2024-26678: In the Linux kernel, the following vulnerability has been resolved: x86/efistub: Use 1:1 file:memory mapping for PE/COFF
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 an
GHSA
GHSA-5g26-fc68-x9f2: In the Linux kernel, the following vulnerability has been resolved:
x86/efistub: Use 1:1 file:memory mapping for PE/COFF
ghsa_unreviewed·2024-04-02
CVE-2024-26678 [MEDIUM] CWE-787 GHSA-5g26-fc68-x9f2: In the Linux kernel, the following vulnerability has been resolved:
x86/efistub: Use 1:1 file:memory mapping for PE/COFF
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 fil
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/0a962f2fbaa976af9eed21d0306370cded485787https://git.kernel.org/stable/c/1ad55cecf22f05f1c884adf63cc09d3c3e609ebfhttps://git.kernel.org/stable/c/4adeeff8c12321cd453412a659c3c0eeb9bb2397https://git.kernel.org/stable/c/d327e961573fc335af0ae8a160302205327e1f4ehttps://git.kernel.org/stable/c/0a962f2fbaa976af9eed21d0306370cded485787https://git.kernel.org/stable/c/1ad55cecf22f05f1c884adf63cc09d3c3e609ebfhttps://git.kernel.org/stable/c/4adeeff8c12321cd453412a659c3c0eeb9bb2397https://git.kernel.org/stable/c/d327e961573fc335af0ae8a160302205327e1f4e
2024-04-02
Published