CVE-2024-35803: linux-libc-dev - Call mixed mode boot services on the firmware's stack

linux Updated 02 Oct 2025

Summary

17/05/2024
No i
Unrated
Not published

CVE-2024-35803: In the Linux kernel, the following vulnerability has been resolved: x86/efistub: Call mixed mode boot services on the firmware's stack Normally, the EFI stub calls into the EFI boot services using the stack that was live... Affects linux versions 5.10.103-1 – 6.9.9-1. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

linux-libc-dev is a package in the Debian operating system that provides the C library development files for the Linux kernel. It is an essential component for building and compiling applications on Debian-based systems. The vulnerability identified as CVE-2024-35803 affects the linux-libc-dev package, potentially exposing systems to security risks.

Vulnerability Detail

The vulnerability in linux-libc-dev arises from the way the EFI stub calls into the EFI boot services using the stack that was live when the stub was entered. In mixed mode, where the bootloader calls the 32-bit EFI stub entry point, the boot stack is set up using a fixed allocation of 16k. This stack is still in use when the EFI stub is started in 64-bit mode, leading to all calls back into the EFI firmware using the limited boot stack. An attacker could exploit this vulnerability to corrupt the end of the .data section, potentially leading to unauthorized access or system instability.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. However, users can mitigate the risk by ensuring they have the latest security updates installed and following best practices for system security.

Conclusion

The vulnerability in linux-libc-dev (CVE-2024-35803) exposes systems to potential security risks. It is crucial to update the linux-libc-dev package to the latest version to mitigate these risks. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

linux-libc-dev is a package in the Debian operating system that provides the C library development files for the Linux kernel. It is used for building and compiling applications on Debian-based systems.

This vulnerability could potentially allow an attacker to corrupt the end of the .data section, leading to unauthorized access or system instability.

To fix this vulnerability, it is recommended to update the linux-libc-dev package to version 6.1.90-1 or later. This can be done by running the package manager update command specific to your operating system.

There is no specific workaround mentioned for this vulnerability. However, users can mitigate the risk by ensuring they have the latest security updates installed and following best practices for system security.

More information about this vulnerability can be found on the Debian Security Tracker website.

Related vulnerabilities

Recent vulnerabilities recorded for linux.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback