Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-27413, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.25% · top 84% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected f24c4d478013d82bd1b943df566fff3561d52864 – < 00cf21ac526011a29fc708f8912da446fac19f7b
    • affected f24c4d478013d82bd1b943df566fff3561d52864 – < 950d4d74d311a18baed6878dbfba8180d7e5dddd
    • affected f24c4d478013d82bd1b943df566fff3561d52864 – < 537e3f49dbe88881a6f0752beaa596942d9efd64
    • affected f24c4d478013d82bd1b943df566fff3561d52864 – < 4b73473c050a612fb4317831371073eda07c3050
    • affected f24c4d478013d82bd1b943df566fff3561d52864 – < ddc547dd05a46720866c32022300f7376c40119f
    • affected f24c4d478013d82bd1b943df566fff3561d52864 – < 11aabd7487857b8e7d768fefb092f66dfde68492
    • affected f24c4d478013d82bd1b943df566fff3561d52864 – < 62a5dcd9bd3097e9813de62fa6f22815e84a0172
    • affected f24c4d478013d82bd1b943df566fff3561d52864 – < fccfa646ef3628097d59f7d9c1a3e84d4b6bb45e
    • affected 95a362c9a6892085f714eb6e31eea6a0e3aa93bf
    • affected 4.14.13 – < 4.15
  • Linux · Linux

    • affected 4.15
    • unaffected < 4.15
    • unaffected 4.19.309 – ≤ 4.19.*
    • unaffected 5.4.271 – ≤ 5.4.*
    • unaffected 5.10.212 – ≤ 5.10.*
    • unaffected 5.15.151 – ≤ 5.15.*
    • unaffected 6.1.81 – ≤ 6.1.*
    • unaffected 6.6.21 – ≤ 6.6.*
    • unaffected 6.7.9 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-27413 badge
[![CVE-2024-27413](https://cveledger.app/badge/CVE-2024-27413.svg)](https://cveledger.app/cve/CVE-2024-27413)

Record last updated .