cve.bz

CVE-2026-46253 linux linux kernel: Out-of-bounds Write

7.8 highEPSS 0.2%Fix available

High (7.8) in linux linux kernel. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: pstore/ram: fix buffer overflow in persistent_ram_save_old() persistent_ram_save_old() can be called multiple times for the same persistent_ram_zone (e.g., via ramoops_pstore_read -> ramoops_get_next_prz for PSTORE_TYPE_DMESG records). Currently, the function only allocates prz->old_log when it is NULL, but it unconditionally updates prz->old_log_size to the current buffer size and then performs memcpy_fromio() using this new size. If the buffer size has grown since the first allocation (which can happen across different kernel boot cycles), this leads to: 1. A heap buffer overflow (OOB write) in the memcpy_fromio() calls 2. A subsequent OOB read when ramoops_pstore_read() accesses the buffer using the incorrect (larger) old_log_size The KASAN splat would look similar to: BUG: KASAN: slab-out-of-bounds in ramoops_pstore_read+0x... Read of size N at addr ... by task ... The conditions are likely extremely hard to hit: 0. Crash with a ramoops write of less-than-record-max-size bytes. 1. Reboot: ramoops registers, pstore_get_records(0) reads old crash, allocates old_log with size X 2. Crash handler registered, timer started (if pstore_update_ms >= 0) 3. Oops happens (non-fatal, system continues) 4. pstore_dump() writes oops via ramoops_pstore_write() size Y (>X) 5. pstore_new_entry = 1, pstore_timer_kick() called 6. System continues running (not a panic oops) 7. Timer fires after pstore_update_ms milliseconds 8. pstore_timefunc() → schedule_work() → pstore_dowork() → pstore_get_records(1) 9. ramoops_get_next_prz() → persistent_ram_save_old() 10. buffer_size() returns Y, but old_log is X bytes 11. Y > X: memcpy_fromio() overflows heap Requirements: - a prior crash record exists that did not fill the record size (almost impossible since the crash handler writes as much as it can possibly fit into the record, capped by max record size and the kmsg buffer almost always exceeds the max record size) - pstore_update_ms >= 0 (disabled by default) - Non-fatal oops (system survives) Free and reallocate the buffer when the new size differs from the previously allocated size. This ensures old_log always has sufficient space for the data being copied.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-787 Out-of-bounds Write
CWE-122 Heap-based Buffer Overflow
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-46253 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-46253?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-46253?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-46253 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux3.5 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.252
Linux5.155.15.202
Linux6.16.1.165
Linux6.66.6.128
Linux6.126.12.75
Linux6.186.18.14
Linux6.196.19.4
Linuxlater releases7.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.170-1DEBIAN-CVE-2026-46253
Debian13linux6.12.85-1DEBIAN-CVE-2026-46253
Debian14linux6.18.14-1DEBIAN-CVE-2026-46253
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-46253
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-46253
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-46253
Ubuntu22.04:LTSlinux5.15.0-186.196UBUNTU-CVE-2026-46253 USN-8575-1
Ubuntu22.04:LTSlinux-aws5.15.0-1112.119UBUNTU-CVE-2026-46253 USN-8575-2
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1060.63~22.04.1UBUNTU-CVE-2026-46253 USN-8492-2
Ubuntu22.04:LTSlinux-azure, linux-azure-fde5.15.0-1117.126UBUNTU-CVE-2026-46253 USN-8575-3 USN-8610-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1063.71~22.04.1UBUNTU-CVE-2026-46253 USN-8606-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1062.69~22.04.1UBUNTU-CVE-2026-46253 USN-8609-1
Ubuntu22.04:LTSlinux-gcp5.15.0-1112.122UBUNTU-CVE-2026-46253 USN-8575-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1063.69~22.04.1UBUNTU-CVE-2026-46253 USN-8492-2
Ubuntu22.04:LTSlinux-gke5.15.0-1108.114UBUNTU-CVE-2026-46253 USN-8575-1
68 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 15 SP4, Linux Enterprise Live Patching 15 SP4kernel-default5.14.21-150400.24.228.1SUSE-SU-2026:3044-1
SUSELinux Enterprise High Availability Extension 15 SP6, Linux Enterprise Live Patching 15 SP6kernel-default6.4.0-150600.23.125.1SUSE-SU-2026:3156-1
SUSELinux Enterprise High Availability Extension 15 SP7, Linux Enterprise Live Patching 15 SP7, Linux Enterprise Module for Legacy 15 SP7 and 1 morekernel-default6.4.0-150700.53.66.1SUSE-SU-2026:2800-1
SUSELinux Enterprise High Availability Extension 16.0kernel-default6.12.0-160000.36.1SUSE-SU-2026:22812-1
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSSkernel-64kb, kernel-docs, kernel-syms and 3 more5.14.21-150400.24.228.1SUSE-SU-2026:3044-1
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise Micro 5.3 and 3 morekernel-default-base5.14.21-150400.24.228.1.150400.24.116.1SUSE-SU-2026:3044-1
SUSELinux Enterprise High Performance Computing 15 SP5-ESPOS, Linux Enterprise High Performance Computing 15 SP5-LTSSkernel-64kb, kernel-docs, kernel-syms and 3 more5.14.21-150500.55.177.1SUSE-SU-2026:3089-1
SUSELinux Enterprise High Performance Computing 15 SP5-ESPOS, Linux Enterprise High Performance Computing 15 SP5-LTSS, Linux Enterprise Micro 5.5 and 2 morekernel-default-base5.14.21-150500.55.177.1.150500.6.83.2SUSE-SU-2026:3089-1
SUSELinux Enterprise Live Patching 12 SP5kernel-default4.12.14-122.320.1SUSE-SU-2026:2914-1
SUSELinux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_851-8.3.1SUSE-SU-2026:2914-1
SUSELinux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_571-150400.9.3.1SUSE-SU-2026:3044-1
SUSELinux Enterprise Live Patching 15 SP5kernel-default5.14.21-150500.55.177.1SUSE-SU-2026:3089-1
31 more for SUSE in the JSON and on SUSE's page.
openSUSELeap 16.0kernel-default-base6.12.0-160000.36.1.160000.2.17openSUSE-SU-2026:21388-1
openSUSELeap 16.0kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160000.36.1openSUSE-SU-2026:21388-1
Alpaquita23linux-lts6.1.167-r0BELL-CVE-2026-46253
Alpaquita25linux-lts6.12.80-r0BELL-CVE-2026-46253
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2026-46253

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A heap OOB write in pstore/ram can occur when persistent_ram_save_old() is called again for the same persistent_ram_zone after the persistent RAM buffer size has grown across boot or crash collection cycles. The old_log buffer may still have the earlier smaller allocation while old_log_size is updated to the newer larger size, so memcpy_fromio can copy past the end of the heap buffer and a later ramoops_pstore_read can perform an OOB read using the larger size. For the CVSS the PR:L value is used in the paranoid vector because an unprivileged local process may be able to reach the affected pstore read or timer paths on a system where ramoops and periodic pstore updates are already enabled, although reliable triggering still requires unusual crash timing and a survivable non-fatal oops. The issue is not network reachable. Impact is at least local denial of service via kernel crash and in worst case may allow confidentiality or integrity impact due to heap memory corruption.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelFix deferred
Red Hat Enterprise Linux 7kernel-rtFix deferred
Red Hat Enterprise Linux 8kernelFix deferred
Red Hat Enterprise Linux 8kernel-rtFix deferred
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-46253.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON