CVE-2026-53047: efi/capsule-loader: fix incorrect sizeof in phys array reallocation
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.17% (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 22022cd8851703a58f67615a17bc7e9e8682785b, 4.15, 48a428215782321b56956974f23593e40ce84b7a; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.143.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 22022cd8851703a58f67615a17bc7e9e8682785b, 4.15, 48a428215782321b56956974f23593e40ce84b7a; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.143.1-1 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 sizeof in phys array reallocation The krealloc() call for cap_info->phys in __efi_capsule_setup_info() uses sizeof(phys_addr_t *) instead of sizeof(phys_addr_t), which might be causing an undersized allocation. The allocation is also inconsistent with the initial array allocation in efi_capsule_open() that allocates one entry with sizeof(phys_addr_t), and the efi_capsule_write() function that stores phys_addr_t values (not pointers) via page_to_phys(). On 64-bit systems where sizeof(phys_addr_t) == sizeof(phys_addr_t *), this goes unnoticed. On 32-bit systems with PAE where phys_addr_t is 64-bit but pointers are 32-bit, this allocates half the required space, which might lead to a heap buffer overflow when storing physical addresses. This is similar to the bug fixed in commit fccfa646ef36 ("efi/capsule-loader: fix incorrect allocation size") which fixed the same issue at the initial allocation site.
- Published
- Jun 24, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.1% · 7th 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.1%
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 |
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 22022cd8851703a58f67615a17bc7e9e8682785baffected · git
- f24c4d478013d82bd1b943df566fff3561d52864 and later · before 67adde6bfdfd563a54b045d59aeb9a2d90c80697affected · git
- f24c4d478013d82bd1b943df566fff3561d52864 and later · before 608e1f7bc9d171ab26c1fba288c97fc76363c27daffected · git
- f24c4d478013d82bd1b943df566fff3561d52864 and later · before 8be69e9245f805566bac68ffc8574b64735fd996affected · git
- f24c4d478013d82bd1b943df566fff3561d52864 and later · before 5e185330d902b12fe8e6eb4b8514b5d736d8d66daffected · git
- f24c4d478013d82bd1b943df566fff3561d52864 and later · before e0e6b14995fd6fa2c0df8c712d76ab32f0694c31affected · git
- f24c4d478013d82bd1b943df566fff3561d52864 and later · before ab3f7098a3a27175b91cfc947950f5c26855801baffected · git
- f24c4d478013d82bd1b943df566fff3561d52864 and later · before 48a428215782321b56956974f23593e40ce84b7aaffected · git
- 4.14.13 and later · before 4.15affected · semver
Affected versions · NVD (9)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.14.13 and later · before 4.15
- linux linux kernel4.15.1 and later · before 5.10.258
- linux linux kernel5.11 and later · before 5.15.209
- linux linux kernel5.16 and later · before 6.1.175
- linux linux kernel6.2 and later · before 6.6.141
- linux linux kernel6.7 and later · before 6.12.91
- linux linux kernel6.13 and later · before 6.18.33
- linux linux kernel6.19 and later · before 7.0.10
- linux linux kernel4.15
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.176-1 | 6.1.176-1 |
| Debian:13 | linux | before 6.12.94-1 | 6.12.94-1 |
| Debian:14 | linux | before 7.0.10-1 | 7.0.10-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-2026-53035Jun 24, 2026 · bpf, sockmap: Fix af_unix iter deadlock22Monitor
- ← EarlierCVE-2026-53037Jun 24, 2026 · HID: usbhid: fix deadlock in hid_post_reset()22Monitor
- Later →CVE-2026-53048Jun 24, 2026 · gfs2: prevent NULL pointer dereference during unmount22Monitor
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 | 22022cd8851703a58f67615a17bc7e9e8682785b | Vendor (CNA) |
| Linux Linux | 4.15 | Vendor (CNA) |
| Linux Linux | 48a428215782321b56956974f23593e40ce84b7a | Vendor (CNA) |
| Linux Linux | 5e185330d902b12fe8e6eb4b8514b5d736d8d66d | Vendor (CNA) |
| Linux Linux | 608e1f7bc9d171ab26c1fba288c97fc76363c27d | Vendor (CNA) |
| Linux Linux | 67adde6bfdfd563a54b045d59aeb9a2d90c80697 | Vendor (CNA) |
| Linux Linux | 8be69e9245f805566bac68ffc8574b64735fd996 | Vendor (CNA) |
| Linux Linux | ab3f7098a3a27175b91cfc947950f5c26855801b | Vendor (CNA) |
| Linux Linux | e0e6b14995fd6fa2c0df8c712d76ab32f0694c31 | Vendor (CNA) |
| azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 | 6.6.143.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.176-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.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0440 · Jun 25, 2026(Linux Kernel Güvenlik Bildirimi)
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 (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/48a428215782321b56956974f23593e40ce84b7a
- git.kernel.org/stable/c/5e185330d902b12fe8e6eb4b8514b5d736d8d66d
- git.kernel.org/stable/c/608e1f7bc9d171ab26c1fba288c97fc76363c27d
- git.kernel.org/stable/c/67adde6bfdfd563a54b045d59aeb9a2d90c80697
- git.kernel.org/stable/c/8be69e9245f805566bac68ffc8574b64735fd996
- git.kernel.org/stable/c/ab3f7098a3a27175b91cfc947950f5c26855801b
- git.kernel.org/stable/c/e0e6b14995fd6fa2c0df8c712d76ab32f0694c31
Vendor advisories and official records. Exploit/PoC links are deliberately left out.