First published: Fri May 17 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: efi: fix panic in kdump kernel Check if get_next_variable() is actually valid pointer before calling it. In kdump kernel this method is set to NULL that causes panic during the kexec-ed kernel boot. Tested with QEMU and OVMF firmware.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/kernel | <6.1.84 | 6.1.84 |
redhat/kernel | <6.6.24 | 6.6.24 |
redhat/kernel | <6.7.12 | 6.7.12 |
redhat/kernel | <6.8.3 | 6.8.3 |
redhat/kernel | <6.9 | 6.9 |
debian/linux | 5.10.223-1 5.10.226-1 6.1.123-1 6.1.119-1 6.12.11-1 6.12.12-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-35800 has been classified as a medium severity vulnerability in the Linux kernel.
To fix CVE-2024-35800, upgrade to kernel versions 6.1.84, 6.6.24, 6.7.12, 6.8.3, 6.9, or the specified versions from Debian.
CVE-2024-35800 may cause a kernel panic during the boot process of a kdump kernel.
CVE-2024-35800 affects certain older versions of the Linux kernel up until the specified patched versions in the remediation.
CVE-2024-35800 does not appear to have a direct remote exploit vector, as it primarily affects local kernel operations.