Linux Kernel up to 7.0.9 efi krealloc phys heap-based overflow

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.6$5k-$25k0.00

Summaryinfo

A vulnerability classified as critical has been found in Linux Kernel up to 7.0.9. Impacted is the function krealloc of the component efi. This manipulation of the argument phys causes heap-based overflow. This vulnerability is tracked as CVE-2026-53047. No exploit exists. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability has been found in Linux Kernel up to 7.0.9 and classified as critical. Affected by this vulnerability is the function krealloc of the component efi. The manipulation of the argument phys with an unknown input leads to a heap-based overflow vulnerability. The CWE definition for the vulnerability is CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-53047 since 06/09/2026. The exploitation appears to be easy. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 06/24/2026).

Upgrading to version 5.10.258, 5.15.209, 6.1.175, 6.6.141, 6.12.91, 6.18.33 or 7.0.10 eliminates this vulnerability. Applying the patch 22022cd8851703a58f67615a17bc7e9e8682785b/67adde6bfdfd563a54b045d59aeb9a2d90c80697/608e1f7bc9d171ab26c1fba288c97fc76363c27d/8be69e9245f805566bac68ffc8574b64735fd996/5e185330d902b12fe8e6eb4b8514b5d736d8d66d/e0e6b14995fd6fa2c0df8c712d76ab32f0694c31/ab3f7098a3a27175b91cfc947950f5c26855801b/48a428215782321b56956974f23593e40ce84b7a is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.0
VulDB Meta Temp Score: 7.6

VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Heap-based overflow
CWE: CWE-122 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.258/5.15.209/6.1.175/6.6.141/6.12.91/6.18.33/7.0.10
Patch: 22022cd8851703a58f67615a17bc7e9e8682785b/67adde6bfdfd563a54b045d59aeb9a2d90c80697/608e1f7bc9d171ab26c1fba288c97fc76363c27d/8be69e9245f805566bac68ffc8574b64735fd996/5e185330d902b12fe8e6eb4b8514b5d736d8d66d/e0e6b14995fd6fa2c0df8c712d76ab32f0694c31/ab3f7098a3a27175b91cfc947950f5c26855801b/48a428215782321b56956974f23593e40ce84b7a

Timelineinfo

06/09/2026 CVE reserved
06/24/2026 +15 days Advisory disclosed
06/24/2026 +0 days VulDB entry created
06/24/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-53047 (🔒)
GCVE (CVE): GCVE-0-2026-53047
GCVE (VulDB): GCVE-100-373477

Entryinfo

Created: 06/24/2026 21:22
Changes: 06/24/2026 21:22 (60)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to know what is going to be exploited?

We predict KEV entries!