CVE-2024-27413: efi/capsule-loader: fix incorrect allocation size
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 00cf21ac526011a29fc708f8912da446fac19f7b, 11aabd7487857b8e7d768fefb092f66dfde68492, 4.15.
Low priority for now. Upgrade to Linux Linux 00cf21ac526011a29fc708f8912da446fac19f7b, 11aabd7487857b8e7d768fefb092f66dfde68492, 4.15 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 17, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- —
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 95a362c9a6892085f714eb6e31eea6a0e3aa93bf, 4.15affected
- f24c4d478013d82bd1b943df566fff3561d52864 and later · before 00cf21ac526011a29fc708f8912da446fac19f7baffected · git
- f24c4d478013d82bd1b943df566fff3561d52864 and later · before 950d4d74d311a18baed6878dbfba8180d7e5ddddaffected · git
- f24c4d478013d82bd1b943df566fff3561d52864 and later · before 537e3f49dbe88881a6f0752beaa596942d9efd64affected · git
- f24c4d478013d82bd1b943df566fff3561d52864 and later · before 4b73473c050a612fb4317831371073eda07c3050affected · git
- f24c4d478013d82bd1b943df566fff3561d52864 and later · before ddc547dd05a46720866c32022300f7376c40119faffected · git
- f24c4d478013d82bd1b943df566fff3561d52864 and later · before 11aabd7487857b8e7d768fefb092f66dfde68492affected · git
- f24c4d478013d82bd1b943df566fff3561d52864 and later · before 62a5dcd9bd3097e9813de62fa6f22815e84a0172affected · git
- f24c4d478013d82bd1b943df566fff3561d52864 and later · before fccfa646ef3628097d59f7d9c1a3e84d4b6bb45eaffected · git
- 4.14.13 and later · before 4.15affected · semver
Affected versions · NVD (11)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- linux linux kernel4.15.1 and later · before 4.19.309
- linux linux kernel4.20 and later · before 5.4.271
- linux linux kernel5.5 and later · before 5.10.212
- linux linux kernel5.11 and later · before 5.15.151
- linux linux kernel4.14.13 and later · before 4.15
- linux linux kernel6.2 and later · before 6.6.21
- linux linux kernel6.7 and later · before 6.7.9
- linux linux kernel5.16 and later · before 6.1.81
- linux linux kernel4.15
- linux linux kernel6.8
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.82-1 | 6.1.82-1 |
| Debian:13 | linux | before 6.7.9-1 | 6.7.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-27411May 17, 2024 · drm/nouveau: keep DMA buffers required for suspend/resume22Monitor
- ← EarlierCVE-2024-27412May 17, 2024 · power: supply: bq27xxx-i2c: Do not free non existing IRQ22Monitor
- Later →CVE-2024-27414May 17, 2024 · rtnetlink: fix error logic of IFLA_BRIDGE_FLAGS writing back22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 00cf21ac526011a29fc708f8912da446fac19f7b | Vendor (CNA) |
| Linux Linux | 11aabd7487857b8e7d768fefb092f66dfde68492 | Vendor (CNA) |
| Linux Linux | 4.15 | Vendor (CNA) |
| Linux Linux | 4b73473c050a612fb4317831371073eda07c3050 | Vendor (CNA) |
| Linux Linux | 537e3f49dbe88881a6f0752beaa596942d9efd64 | Vendor (CNA) |
| Linux Linux | 62a5dcd9bd3097e9813de62fa6f22815e84a0172 | Vendor (CNA) |
| Linux Linux | 950d4d74d311a18baed6878dbfba8180d7e5dddd | Vendor (CNA) |
| Linux Linux | ddc547dd05a46720866c32022300f7376c40119f | Vendor (CNA) |
| Linux Linux | fccfa646ef3628097d59f7d9c1a3e84d4b6bb45e | Vendor (CNA) |
| debian:linux | 6.1.82-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/11aabd7487857b8e7d768fefb092f66dfde68492
- git.kernel.org/stable/c/4b73473c050a612fb4317831371073eda07c3050
- git.kernel.org/stable/c/537e3f49dbe88881a6f0752beaa596942d9efd64
- git.kernel.org/stable/c/62a5dcd9bd3097e9813de62fa6f22815e84a0172
- git.kernel.org/stable/c/950d4d74d311a18baed6878dbfba8180d7e5dddd
- git.kernel.org/stable/c/ddc547dd05a46720866c32022300f7376c40119f
- git.kernel.org/stable/c/fccfa646ef3628097d59f7d9c1a3e84d4b6bb45e
- lists.debian.org/debian-lts-announce/2024/06/msg00017.html
- lists.debian.org/debian-lts-announce/2024/06/msg00020.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.