CVE-2026-53047None▾ SunlitIn 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 *) ins…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.
Exploit-prediction probability, daily snapshots since Nov 6.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.2%
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.
Linux >= f24c4d478013d82bd1b943df566fff3561d52864 < 22022cd8851703a58f67615a17bc7e9e8682785bLinux >= f24c4d478013d82bd1b943df566fff3561d52864 < 67adde6bfdfd563a54b045d59aeb9a2d90c80697Linux >= f24c4d478013d82bd1b943df566fff3561d52864 < 608e1f7bc9d171ab26c1fba288c97fc76363c27dLinux >= f24c4d478013d82bd1b943df566fff3561d52864 < 8be69e9245f805566bac68ffc8574b64735fd996Linux >= f24c4d478013d82bd1b943df566fff3561d52864 < 5e185330d902b12fe8e6eb4b8514b5d736d8d66dLinux >= f24c4d478013d82bd1b943df566fff3561d52864 < e0e6b14995fd6fa2c0df8c712d76ab32f0694c31Linux >= f24c4d478013d82bd1b943df566fff3561d52864 < ab3f7098a3a27175b91cfc947950f5c26855801bLinux >= f24c4d478013d82bd1b943df566fff3561d52864 < 48a428215782321b56956974f23593e40ce84b7aLinux 95a362c9a6892085f714eb6e31eea6a0e3aa93bfLinux >= 4.14.13 < 4.15Linux 4.15Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99284Nonenet: skbuff: propagate shared-frag marker in skb_zerocopy()
CVE-2026-99283Nonenetfilter: conntrack: tcp: use UNACK timeout for non-closing RST packets
CVE-2026-99272Nonesmb: client: validate the data area in SMB2_read()
CVE-2026-99271NoneALSA: line6: Clear prev_fbuf on capture buffer release
CVE-2026-99273Noneksmbd: reserve space for the UTF-16 terminator in stream info
CVE-2026-99275Nonesmb: client: reject short SESSION_SETUP responses