CVE-2026-53047

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-24. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 21, 2026

Advisory Details (8)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

efi/capsule-loader: fix incorrect sizeof in phys array reallocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e0e6b14995fd6fa2c0df8c712d76ab32f0694c31
generic

efi/capsule-loader: fix incorrect sizeof in phys array reallocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ab3f7098a3a27175b91cfc947950f5c26855801b
generic

efi/capsule-loader: fix incorrect sizeof in phys array reallocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8be69e9245f805566bac68ffc8574b64735fd996
generic

efi/capsule-loader: fix incorrect sizeof in phys array reallocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/67adde6bfdfd563a54b045d59aeb9a2d90c80697
generic

efi/capsule-loader: fix incorrect sizeof in phys array reallocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/608e1f7bc9d171ab26c1fba288c97fc76363c27d
generic

efi/capsule-loader: fix incorrect sizeof in phys array reallocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5e185330d902b12fe8e6eb4b8514b5d736d8d66d
generic

efi/capsule-loader: fix incorrect sizeof in phys array reallocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/48a428215782321b56956974f23593e40ce84b7a
generic

efi/capsule-loader: fix incorrect sizeof in phys array reallocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/22022cd8851703a58f67615a17bc7e9e8682785b

Vendor Advisories for CVE-2026-53047(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-08-30ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-30ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-30ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-08-30ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-30ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-30ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-08-30ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-08-30ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-30ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-30ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-08-30ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-30ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-30ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-30ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-30ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-30ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-08-30ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-30ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-30ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-30ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-08-30ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-08-30ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-08-30ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-08-30ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1—

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 64× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 187 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-02 14:12 UTCEPSS rescore
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 04:40 UTCEPSS rescore
  10. 2026-08-30 20:05 UTCEG score recompute
  11. 2026-08-30 20:05 UTCVendor advisory
  12. 2026-08-30 20:04 UTCGHSA enrichment
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-28 03:49 UTCEG score recompute
  17. 2026-08-28 03:49 UTCVendor advisory
  18. 2026-08-28 03:48 UTCGHSA enrichment
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-24 13:39 UTCEG score recompute
  23. 2026-08-24 13:39 UTCVendor advisory
  24. 2026-08-24 13:39 UTCGHSA enrichment
  25. 2026-08-23 09:37 UTCEG score recompute
Show 75 more
  1. 2026-08-23 09:37 UTCVendor advisory
  2. 2026-08-23 09:37 UTCGHSA enrichment
  3. 2026-08-23 00:19 UTCEPSS rescore
  4. 2026-08-22 11:39 UTCEG score recompute
  5. 2026-08-22 11:39 UTCVendor advisory
  6. 2026-08-22 11:38 UTCGHSA enrichment
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-21 05:21 UTCEG score recompute
  9. 2026-08-21 05:21 UTCVendor advisory
  10. 2026-08-21 05:20 UTCGHSA enrichment
  11. 2026-08-20 22:55 UTCEPSS rescore
  12. 2026-08-20 07:25 UTCVendor advisory
  13. 2026-08-20 07:24 UTCGHSA enrichment
  14. 2026-08-19 02:08 UTCEG score recompute
  15. 2026-08-19 02:08 UTCVendor advisory
  16. 2026-08-19 02:07 UTCGHSA enrichment
  17. 2026-08-18 13:48 UTCEPSS rescore
  18. 2026-08-17 13:53 UTCEG score recompute
  19. 2026-08-17 13:53 UTCVendor advisory
  20. 2026-08-17 13:53 UTCGHSA enrichment
  21. 2026-08-17 13:47 UTCEPSS rescore
  22. 2026-08-16 16:00 UTCEG score recompute
  23. 2026-08-16 16:00 UTCVendor advisory
  24. 2026-08-16 16:00 UTCGHSA enrichment
  25. 2026-08-16 14:56 UTCEPSS rescore
  26. 2026-08-16 02:14 UTCEPSS rescore
  27. 2026-08-15 18:07 UTCEG score recompute
  28. 2026-08-15 18:07 UTCVendor advisory
  29. 2026-08-15 18:07 UTCGHSA enrichment
  30. 2026-08-15 01:30 UTCEPSS rescore
  31. 2026-08-14 20:13 UTCVendor advisory
  32. 2026-08-14 20:13 UTCGHSA enrichment
  33. 2026-08-13 22:20 UTCEG score recompute
  34. 2026-08-13 22:20 UTCVendor advisory
  35. 2026-08-13 22:20 UTCGHSA enrichment
  36. 2026-08-13 22:00 UTCEPSS rescore
  37. 2026-08-13 00:27 UTCEG score recompute
  38. 2026-08-13 00:27 UTCVendor advisory
  39. 2026-08-13 00:27 UTCGHSA enrichment
  40. 2026-08-12 13:51 UTCEPSS rescore
  41. 2026-08-12 02:34 UTCVendor advisory
  42. 2026-08-12 02:34 UTCGHSA enrichment
  43. 2026-08-11 04:40 UTCEG score recompute
  44. 2026-08-11 04:40 UTCVendor advisory
  45. 2026-08-11 04:40 UTCGHSA enrichment
  46. 2026-08-11 00:00 UTCEPSS rescore
  47. 2026-08-10 06:47 UTCEG score recompute
  48. 2026-08-10 06:47 UTCVendor advisory
  49. 2026-08-10 06:47 UTCGHSA enrichment
  50. 2026-08-09 13:46 UTCEPSS rescore
  51. 2026-08-09 08:54 UTCEG score recompute
  52. 2026-08-09 08:54 UTCVendor advisory
  53. 2026-08-09 08:54 UTCGHSA enrichment
  54. 2026-08-08 16:37 UTCEPSS rescore
  55. 2026-08-08 11:01 UTCEG score recompute
  56. 2026-08-08 11:01 UTCVendor advisory
  57. 2026-08-08 11:01 UTCGHSA enrichment
  58. 2026-08-07 13:08 UTCVendor advisory
  59. 2026-08-07 13:08 UTCGHSA enrichment
  60. 2026-08-06 15:14 UTCEG score recompute
  61. 2026-08-06 15:14 UTCVendor advisory
  62. 2026-08-06 15:14 UTCGHSA enrichment
  63. 2026-08-06 13:47 UTCEPSS rescore
  64. 2026-08-05 19:17 UTCEPSS rescore
  65. 2026-08-05 17:21 UTCVendor advisory
  66. 2026-08-05 17:21 UTCGHSA enrichment
  67. 2026-08-04 15:10 UTCEG score recompute
  68. 2026-08-04 15:10 UTCVendor advisory
  69. 2026-08-04 15:10 UTCGHSA enrichment
  70. 2026-08-04 15:10 UTCEPSS rescore
  71. 2026-08-04 10:39 UTCEPSS rescore
  72. 2026-08-03 15:59 UTCEG score recompute
  73. 2026-08-03 15:59 UTCVendor advisory
  74. 2026-08-03 15:59 UTCGHSA enrichment
  75. 2026-08-03 10:36 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-53047?
CVE-2026-53047 is a medium vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: efi/capsule-loader: fix incorrect sizeof in phys array reallocation The krealloc() call for capinfo->phys in eficapsulesetupinfo() uses sizeof(physaddrt *) instead of sizeof(physaddrt), which might be causing an undersized…
When was CVE-2026-53047 disclosed?
CVE-2026-53047 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53047 actively exploited?
CVE-2026-53047 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.7% of all scored CVEs.
What is the CVSS score of CVE-2026-53047?
CVE-2026-53047 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53047?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53047, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53047

Explore →

Is Your Infrastructure Affected by CVE-2026-53047?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs