CVE-2026-46253 — linux / linux_kernel
Out-of-bounds WriteIn 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:
- A heap buffer overflow (OOB write) in the memcpy_fromio() calls
- 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:
- Crash with a ramoops write of less-than-record-max-size bytes.
- Reboot: ramoops registers, pstore_get_records(0) reads old crash, allocates old_log with size X
- Crash handler registered, timer started (if pstore_update_ms >= 0)
- Oops happens (non-fatal, system continues)
- pstore_dump() writes oops via ramoops_pstore_write() size Y (>X)
- pstore_new_entry = 1, pstore_timer_kick() called
- System continues running (not a panic oops)
- Timer fires after pstore_update_ms milliseconds
- pstore_timefunc() → schedule_work() → pstore_dowork() → pstore_get_records(1)
- ramoops_get_next_prz() → persistent_ram_save_old()
- buffer_size() returns Y, but old_log is X bytes
- 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.
| Software | Affected versions |
|---|---|
| linux / linux_kernel | >= 3.5.1, < 5.10.252 |
| linux / linux_kernel | >= 5.11, < 5.15.202 |
| linux / linux_kernel | >= 5.16, < 6.1.165 |
| linux / linux_kernel | >= 6.2, < 6.6.128 |
| linux / linux_kernel | >= 6.7, < 6.12.75 |
| linux / linux_kernel | >= 6.13, < 6.18.14 |
| linux / linux_kernel | >= 6.19, < 6.19.4 |
| linux / linux_kernel | = 3.5 |
| linux / linux_kernel | = 3.5-rc4 |
| linux / linux_kernel | = 3.5-rc5 |
| linux / linux_kernel | = 3.5-rc6 |
| linux / linux_kernel | = 3.5-rc7 |
- https://git.kernel.org/stable/c/06d2c8bd108cea503f6f6e13e47495ed1085275f
- https://git.kernel.org/stable/c/2fa9a047c6a50ec80c3890dd623b85e237f0d1fd
- https://git.kernel.org/stable/c/4f73486ca822305c1cf5b8ebc0b53a6ab3801a81
- https://git.kernel.org/stable/c/5669645c052f235726a85f443769b6fc02f66762
- https://git.kernel.org/stable/c/58bda5a1d1ee98254383ef34f76b2c35140513ea
- https://git.kernel.org/stable/c/7cfe964e61c0ab667abd5f5b68e0acbf783efa4f
- https://git.kernel.org/stable/c/9a6fc69a570c0780834246d52c856cc3dbc2605f
- https://git.kernel.org/stable/c/cff0ef043e16feb5a02307c8f9d0117a96c5587c
Is CVE-2026-46253 exposed on your perimeter?
A vulnerability database tells you what is broken. Attack surface management tells you where it is running: it discovers your internet-facing assets and flags the ones affected by issues like this one.
What is attack surface management? →
Deep Security Visibility Without the Complexity
SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.
- No setup fees
- 5-min deployment
- Cancel anytime
Frequently Asked Questions
A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.
CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.
A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.
Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.
Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.
SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.