LiveActive security incident?Get immediate response
CVE Record

CVE-2024-27413: efi/capsule-loader: fix incorrect allocation size

In the Linux kernel, the following vulnerability has been resolved: efi/capsule-loader: fix incorrect allocation size gcc-14 notices that the allocation with sizeof(void) on 32-bit architectures is not enough for a 64-bit phys_addr_t: drivers/firmware/efi/capsule-loader.c: In function 'efi_capsule_open': drivers/firmware/efi/capsule-loader.c:295:24: error: allocation of insufficient size '4' for type 'phys_addr_t' {aka 'long long unsigned int'} with size '8' [-Werror=alloc-size] 295 | cap_info->phys = kzalloc(sizeof(void *), GFP_KERNEL); | ^ Use the correct type instead here.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a small but security-relevant memory allocation bug in the EFI capsule loader. On some 32-bit systems, the kernel allocated too little space for a physical address value. The source bundle does not provide a CVSS score, impact rating, or evidence of active exploitation.

Executive priority

Schedule this with regular kernel patching unless the environment has exposed EFI capsule update workflows or high-value 32-bit Linux systems. Escalate if a vendor advisory assigns severity or reports exploitation.

Technical view

The bug is in drivers/firmware/efi/capsule-loader.c. Code allocated sizeof(void *) for cap_info->phys, which can be 4 bytes on 32-bit builds while phys_addr_t may require 8 bytes. The fix changes the allocation to the correct type size. Affected Linux stable lines are listed in the CVE data.

Likely exposure

Exposure is most plausible on Linux systems using affected kernel versions with EFI capsule loader support, especially 32-bit architectures where phys_addr_t is larger than a pointer. The bundle does not identify specific distributions beyond Debian LTS advisories.

Exploitation context

The provided sources show no CISA KEV listing, no public exploitation evidence, and no exploit details. Treat this as a kernel maintenance and hardening issue unless vendor advisories add impact or exploitation evidence.

Researcher notes

The evidence is narrow: compiler diagnostics identified an insufficient allocation size in EFI capsule-loader. The bundle does not state exploitability, privilege requirements, or impact outcome. Analysis should avoid assuming memory corruption reachability beyond the described allocation mismatch.

Mitigation direction

  • Update affected Linux kernels through the normal vendor-supported update channel.
  • For Debian systems, review the cited Debian LTS advisories and apply relevant kernel packages.
  • Confirm the deployed kernel includes the referenced stable fix commit for its branch.
  • Prioritize systems that support UEFI capsule firmware update workflows.
  • Monitor Linux and distribution advisories for any later impact clarification.

Validation and detection

  • Inventory Linux kernel versions, architecture, and distribution package release levels.
  • Compare deployed kernels with the affected and fixed versions in CVE records.
  • Review kernel configuration or package metadata for EFI capsule loader support.
  • Confirm patch status using vendor advisories or stable branch commit references.
  • Document any systems deferred from update and their compensating rationale.
Prepared
Confidence
medium
Sources
12

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-27413 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
11Source 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
LinuxLinuxf24c4d478013d82bd1b943df566fff3561d52864, f24c4d478013d82bd1b943df566fff3561d52864, f24c4d478013d82bd1b943df566fff3561d52864, f24c4d478013d82bd1b943df566fff3561d52864, f24c4d478013d82bd1b943df566fff3561d52864, f24c4d478013d82bd1b943df566fff3561d52864, f24c4d478013d82bd1b943df566fff3561d52864, f24c4d478013d82bd1b943df566fff3561d52864, 95a362c9a6892085f714eb6e31eea6a0e3aa93bf, 4.14.13unaffected
LinuxLinux4.15, 0, 4.19.309, 5.4.271, 5.10.212, 5.15.151, 6.1.81, 6.6.21, 6.7.9, 6.8affected
Weakness

CWE details

No CWE listed

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