CVE-2026-53047 json
efi/capsule-loader: fix incorrect sizeof in phys array reallocation
published 4mo ago modified 5d ago also EUVD-2026-38915
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 4.15, 5.10.258, 5.15.209, 6.1.175, 6.6.141, 6.12.91, 6.18.33, 7.0.10, 7.1
- linux Debian 12 6.1.176-1
- linux Debian 13 6.12.94-1
- linux Debian 14 7.0.10-1
debian advisories DEBIAN-CVE-2026-53047
- linux Ubuntu 22.04 LTS 5.15.0-186.196
- linux Ubuntu 24.04 LTS 6.8.0-136.136
- linux Ubuntu 26.04 LTS 7.0.0-28.28
- linux-aws Ubuntu 22.04 LTS 5.15.0-1112.119
- linux-aws Ubuntu 24.04 LTS 6.8.0-1061.64
- linux-aws Ubuntu 26.04 LTS 7.0.0-1009.9
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1112.122
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1064.72
ubuntu advisories UBUNTU-CVE-2026-53047
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source Linux Micro 6.1, Linux Micro 6.0 6.4.0-51.1
- kernel-default Linux Micro 6.1, Linux Micro 6.0 6.4.0-51.1
- kernel-kvmsmall Linux Micro 6.1, Linux Micro 6.0 6.4.0-51.1
- kernel-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-51.1
- kernel-source-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-51.1
- kernel-default SLES 16.0, SLE High Availability Extension 16.0, Linux Micro 6.2 +1 more 6.12.0-160000.37.1
- kernel-rt Linux Micro 6.2 6.12.0-160000.37.1
- kernel-64kb SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 6.12.0-160000.37.1
suse advisories SUSE-SU-2026:23244-1SUSE-SU-2026:23241-1SUSE-SU-2026:23194-1SUSE-SU-2026:23193-1SUSE-SU-2026:23237-1SUSE-SU-2026:23068-1
- kernel-rt openSUSE Leap 16.0 6.12.0-160000.37.1
- dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.37.1
- kernel-64kb openSUSE Leap 16.0 6.12.0-160000.37.1
- kernel-syms openSUSE Leap 16.0 6.12.0-160000.37.1
- kernel-azure openSUSE Leap 16.0 6.12.0-160000.37.1
- kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.37.1
- kernel-source openSUSE Leap 16.0 6.12.0-160000.37.1
- kernel-default openSUSE Leap 16.0 6.12.0-160000.37.1
opensuse advisories openSUSE-SU-2026:21555-1
- git.kernel.org/stable/c/22022cd8851703a58f67615a17bc7e9e8682785b commit
- git.kernel.org/stable/c/67adde6bfdfd563a54b045d59aeb9a2d90c80697 commit
- git.kernel.org/stable/c/608e1f7bc9d171ab26c1fba288c97fc76363c27d commit
- git.kernel.org/stable/c/8be69e9245f805566bac68ffc8574b64735fd996 commit
- git.kernel.org/stable/c/5e185330d902b12fe8e6eb4b8514b5d736d8d66d commit
- git.kernel.org/stable/c/e0e6b14995fd6fa2c0df8c712d76ab32f0694c31 commit
- git.kernel.org/stable/c/ab3f7098a3a27175b91cfc947950f5c26855801b commit
- git.kernel.org/stable/c/48a428215782321b56956974f23593e40ce84b7a commit
Is CVE-2026-53047 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-53047 updated cvss 4.7
kernel: efi/capsule-loader: fix incorrect sizeof in phys array reallocation
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 moreaffected: workaround, no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5d ago
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/22022cd8851703a58f67615a17bc7e9e8682785b
patch
-
git.kernel.org
/stable/c/67adde6bfdfd563a54b045d59aeb9a2d90c80697
patch
-
git.kernel.org
/stable/c/608e1f7bc9d171ab26c1fba288c97fc76363c27d
patch
-
git.kernel.org
/stable/c/8be69e9245f805566bac68ffc8574b64735fd996
patch
-
git.kernel.org
/stable/c/5e185330d902b12fe8e6eb4b8514b5d736d8d66d
patch
-
git.kernel.org
/stable/c/e0e6b14995fd6fa2c0df8c712d76ab32f0694c31
patch
-
git.kernel.org
/stable/c/ab3f7098a3a27175b91cfc947950f5c26855801b
patch
-
git.kernel.org
/stable/c/48a428215782321b56956974f23593e40ce84b7a
patch
Sources
- CVE List CVE-2026-53047
- NVD CVE-2026-53047
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.