LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can make a crash-recovery kernel panic while booting under EFI, disrupting kdump collection. Business impact is mainly loss of crash diagnostics and recovery confidence, not demonstrated remote compromise. The supplied sources do not provide CVSS, CWE, or active-exploitation evidence.

Executive priority

Treat as a targeted operational reliability fix. Patch through normal kernel maintenance, faster for systems where crash dumps support outage diagnosis, compliance evidence, or post-incident analysis.

Technical view

The EFI path called get_next_variable() without confirming the function pointer was valid. In the kdump kernel this pointer can be NULL, causing a panic during the kexec-ed kernel boot. Kernel stable commits add the validity check.

Likely exposure

Likely exposure is Linux systems using EFI and kdump/crash-kernel workflows on affected kernel branches or commits. The source bundle lists Linux as affected but gives incomplete version semantics, so confirm exact exposure with distribution kernel advisories.

Exploitation context

No supplied source reports active exploitation, and KEV is false. The described failure is a kernel panic during kdump boot, suggesting operational availability and incident-response impact rather than a proven attacker-driven exploitation path.

Researcher notes

Evidence is limited to the CVE record and kernel stable references. No CVSS, CWE, exploitability analysis, or distribution-specific fixed versions are provided in the bundle. Avoid inferring broader privilege escalation or remote attackability.

Mitigation direction

  • Update to a kernel containing the referenced stable fix commits.
  • Check your Linux distribution advisory for fixed package versions.
  • Prioritize systems where kdump is required for incident response or uptime analysis.
  • Document any temporary kdump limitations until patched.

Validation and detection

  • Inventory Linux hosts using EFI with kdump enabled.
  • Compare running kernel builds against vendor fixed-version guidance.
  • Review crash or boot logs for kdump kernel EFI panics.
  • Test kdump boot behavior after kernel updates in staging.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-35800 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxa8901f331b8b7f95a7315d033a22bc84c8365f35, bad267f9e18f8e9e628abd1811d2899b1735a4e1, bad267f9e18f8e9e628abd1811d2899b1735a4e1, bad267f9e18f8e9e628abd1811d2899b1735a4e1, bad267f9e18f8e9e628abd1811d2899b1735a4e1unaffected
LinuxLinux6.3, 0, 6.1.84, 6.6.24, 6.7.12, 6.8.3, 6.9affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.