CVE-2026-46253

Kernel memory corruption via stale crash-log allocation

Published Jun 3, 2026 · Updated Jun 3, 2026

Out-of-bounds write in Linux Kernel pstore/ram allows local users to corrupt kernel memory through a persistent crash-log size change. The persistent_ram_save_old() function retains its first old_log allocation, overwrites old_log_size with a larger current size, and passes that size to memcpy_fromio(), causing an out-of-bounds write and later read. Reachability requires ramoops, a smaller prior crash record, a reboot, pstore_update_ms enabled, and a survivable oops that produces a larger record; corruption can expose kernel memory, alter it, or interrupt the system.

CVSS severity7.8
High
EPSS probability0.14%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Out-of-bounds write in Linux Kernel pstore/ram allows local users to corrupt kernel memory through a persistent crash-log size change. The persistent_ram_save_old() function retains its first old_log allocation, overwrites old_log_size with a larger current size, and passes that size to memcpy_fromio(), causing an out-of-bounds write and later read. Reachability requires ramoops, a smaller prior crash record, a reboot, pstore_update_ms enabled, and a survivable oops that produces a larger record; corruption can expose kernel memory, alter it, or interrupt the system.

The record

CVE
CVE-2026-46253
Published
Jun 3, 2026
Updated
Jun 3, 2026
Vendor
The Linux Kernel Organization
Product
Linux Kernel
Classifications
CWE-787, T1068
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jun 3, 2026CVE publishedPublication date reported by the CVE source.
  2. Jun 3, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=201e4aca5aa179e6c69a4dcd36a3562e56b8d670 <06d2c8bd108cea503f6f6e13e47495ed1085275f
  2. Affected versionversion=201e4aca5aa179e6c69a4dcd36a3562e56b8d670 <2fa9a047c6a50ec80c3890dd623b85e237f0d1fd
  3. Affected versionversion=201e4aca5aa179e6c69a4dcd36a3562e56b8d670 <4f73486ca822305c1cf5b8ebc0b53a6ab3801a81
  4. Affected versionversion=201e4aca5aa179e6c69a4dcd36a3562e56b8d670 <5669645c052f235726a85f443769b6fc02f66762
  5. Affected versionversion=201e4aca5aa179e6c69a4dcd36a3562e56b8d670 <58bda5a1d1ee98254383ef34f76b2c35140513ea
  6. Affected versionversion=201e4aca5aa179e6c69a4dcd36a3562e56b8d670 <7cfe964e61c0ab667abd5f5b68e0acbf783efa4f
  7. Affected versionversion=201e4aca5aa179e6c69a4dcd36a3562e56b8d670 <9a6fc69a570c0780834246d52c856cc3dbc2605f
  8. Affected versionversion=201e4aca5aa179e6c69a4dcd36a3562e56b8d670 <cff0ef043e16feb5a02307c8f9d0117a96c5587c
  9. Affected versionversion=3.5

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linux Kernelversion=201e4aca5aa179e6c69a4dcd36a3562e56b8d670 <06d2c8bd108cea503f6f6e13e47495ed1085275f; version=201e4aca5aa179e6c69a4dcd36a3562e56b8d670 <2fa9a047c6a50ec80c3890dd623b85e237f0d1fd; version=201e4aca5aa179e6c69a4dcd36a3562e56b8d670 <4f73486ca822305c1cf5b8ebc0b53a6ab3801a81; version=201e4aca5aa179e6c69a4dcd36a3562e56b8d670 <5669645c052f235726a85f443769b6fc02f66762; version=201e4aca5aa179e6c69a4dcd36a3562e56b8d670 <58bda5a1d1ee98254383ef34f76b2c35140513ea; version=201e4aca5aa179e6c69a4dcd36a3562e56b8d670 <7cfe964e61c0ab667abd5f5b68e0acbf783efa4f; version=201e4aca5aa179e6c69a4dcd36a3562e56b8d670 <9a6fc69a570c0780834246d52c856cc3dbc2605f; version=201e4aca5aa179e6c69a4dcd36a3562e56b8d670 <cff0ef043e16feb5a02307c8f9d0117a96c5587c; version=3.5

Published CVSS scores

7.8kernel.orgCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-787Out-of-bounds Write
T1068Exploitation for Privilege Escalation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo