# CVE-2024-33619: efi: libstub: only free priv.runtime_map when allocated

> An attacker can cause a denial of service in the Linux kernel by triggering an error path that frees uninitialized memory in the EFI stub.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jun 2024
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2024-33619, DEBIAN-CVE-2024-33619, GHSA-9m7h-hjwm-6r7m, UBUNTU-CVE-2024-33619

## What is CVE-2024-33619?

CVE-2024-33619 is a high-severity vulnerability in Linux kernel, published on 21 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

efi: libstub: only free priv.runtime_map when allocated

priv.runtime_map is only allocated when efi_novamap is not set.
Otherwise, it is an uninitialized value.  In the error path, it is freed
unconditionally.  Avoid passing an uninitialized value to free_pool.
Free priv.runtime_map only when it was allocated.

This bug was discovered and resolved using Coverity Static Analysis
Security Testing (SAST) by Synopsys, Inc.

Weakness: CWE-908 (Use of Uninitialized Resource)

## Which versions are affected by CVE-2024-33619?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-33619?

Apply the vendor's patch.

## Is CVE-2024-33619 being exploited?

There is no known exploitation of CVE-2024-33619 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-33619 and fix it if it is affected.

What it is: CVE-2024-33619 is a high-severity vulnerability in Linux kernel, published on 21 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-33619 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-33619/ (Markdown: https://insights.sbomify.com/CVE-2024-33619/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-33619
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-33619
- OSV: https://osv.dev/vulnerability/CVE-2024-33619

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-33619/
Summaries are generated and may contain mistakes; the official description above is the record.