{"api_version":"1","generated_at":"2026-06-03T19:46:57+00:00","cve":"CVE-2026-46253","urls":{"html":"https://cve.report/CVE-2026-46253","api":"https://cve.report/api/cve/CVE-2026-46253.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-46253","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-46253"},"summary":{"title":"pstore/ram: fix buffer overflow in persistent_ram_save_old()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\npstore/ram: fix buffer overflow in persistent_ram_save_old()\n\npersistent_ram_save_old() can be called multiple times for the same\npersistent_ram_zone (e.g., via ramoops_pstore_read -> ramoops_get_next_prz\nfor PSTORE_TYPE_DMESG records).\n\nCurrently, the function only allocates prz->old_log when it is NULL,\nbut it unconditionally updates prz->old_log_size to the current buffer\nsize and then performs memcpy_fromio() using this new size. If the\nbuffer size has grown since the first allocation (which can happen\nacross different kernel boot cycles), this leads to:\n\n1. A heap buffer overflow (OOB write) in the memcpy_fromio() calls\n2. A subsequent OOB read when ramoops_pstore_read() accesses the buffer\n   using the incorrect (larger) old_log_size\n\nThe KASAN splat would look similar to:\n  BUG: KASAN: slab-out-of-bounds in ramoops_pstore_read+0x...\n  Read of size N at addr ... by task ...\n\nThe conditions are likely extremely hard to hit:\n\n  0. Crash with a ramoops write of less-than-record-max-size bytes.\n  1. Reboot: ramoops registers, pstore_get_records(0) reads old crash,\n     allocates old_log with size X\n  2. Crash handler registered, timer started (if pstore_update_ms >= 0)\n  3. Oops happens (non-fatal, system continues)\n  4. pstore_dump() writes oops via ramoops_pstore_write() size Y (>X)\n  5. pstore_new_entry = 1, pstore_timer_kick() called\n  6. System continues running (not a panic oops)\n  7. Timer fires after pstore_update_ms milliseconds\n  8. pstore_timefunc() → schedule_work() → pstore_dowork() → pstore_get_records(1)\n  9. ramoops_get_next_prz() → persistent_ram_save_old()\n 10. buffer_size() returns Y, but old_log is X bytes\n 11. Y > X: memcpy_fromio() overflows heap\n\n  Requirements:\n  - a prior crash record exists that did not fill the record size\n    (almost impossible since the crash handler writes as much as it\n    can possibly fit into the record, capped by max record size and\n    the kmsg buffer almost always exceeds the max record size)\n  - pstore_update_ms >= 0 (disabled by default)\n  - Non-fatal oops (system survives)\n\nFree and reallocate the buffer when the new size differs from the\npreviously allocated size. This ensures old_log always has sufficient\nspace for the data being copied.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-06-03 18:16:26","updated_at":"2026-06-03 18:16:26"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/4f73486ca822305c1cf5b8ebc0b53a6ab3801a81","name":"https://git.kernel.org/stable/c/4f73486ca822305c1cf5b8ebc0b53a6ab3801a81","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/06d2c8bd108cea503f6f6e13e47495ed1085275f","name":"https://git.kernel.org/stable/c/06d2c8bd108cea503f6f6e13e47495ed1085275f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/5669645c052f235726a85f443769b6fc02f66762","name":"https://git.kernel.org/stable/c/5669645c052f235726a85f443769b6fc02f66762","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/58bda5a1d1ee98254383ef34f76b2c35140513ea","name":"https://git.kernel.org/stable/c/58bda5a1d1ee98254383ef34f76b2c35140513ea","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/cff0ef043e16feb5a02307c8f9d0117a96c5587c","name":"https://git.kernel.org/stable/c/cff0ef043e16feb5a02307c8f9d0117a96c5587c","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/9a6fc69a570c0780834246d52c856cc3dbc2605f","name":"https://git.kernel.org/stable/c/9a6fc69a570c0780834246d52c856cc3dbc2605f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/7cfe964e61c0ab667abd5f5b68e0acbf783efa4f","name":"https://git.kernel.org/stable/c/7cfe964e61c0ab667abd5f5b68e0acbf783efa4f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/2fa9a047c6a50ec80c3890dd623b85e237f0d1fd","name":"https://git.kernel.org/stable/c/2fa9a047c6a50ec80c3890dd623b85e237f0d1fd","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-46253","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46253","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 201e4aca5aa179e6c69a4dcd36a3562e56b8d670 58bda5a1d1ee98254383ef34f76b2c35140513ea git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 201e4aca5aa179e6c69a4dcd36a3562e56b8d670 06d2c8bd108cea503f6f6e13e47495ed1085275f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 201e4aca5aa179e6c69a4dcd36a3562e56b8d670 2fa9a047c6a50ec80c3890dd623b85e237f0d1fd git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 201e4aca5aa179e6c69a4dcd36a3562e56b8d670 cff0ef043e16feb5a02307c8f9d0117a96c5587c git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 201e4aca5aa179e6c69a4dcd36a3562e56b8d670 9a6fc69a570c0780834246d52c856cc3dbc2605f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 201e4aca5aa179e6c69a4dcd36a3562e56b8d670 4f73486ca822305c1cf5b8ebc0b53a6ab3801a81 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 201e4aca5aa179e6c69a4dcd36a3562e56b8d670 7cfe964e61c0ab667abd5f5b68e0acbf783efa4f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 201e4aca5aa179e6c69a4dcd36a3562e56b8d670 5669645c052f235726a85f443769b6fc02f66762 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3.5","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 3.5 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.10.252 5.10.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.15.202 5.15.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.1.165 6.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6.128 6.6.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.75 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.14 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.19.4 6.19.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["fs/pstore/ram_core.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"58bda5a1d1ee98254383ef34f76b2c35140513ea","status":"affected","version":"201e4aca5aa179e6c69a4dcd36a3562e56b8d670","versionType":"git"},{"lessThan":"06d2c8bd108cea503f6f6e13e47495ed1085275f","status":"affected","version":"201e4aca5aa179e6c69a4dcd36a3562e56b8d670","versionType":"git"},{"lessThan":"2fa9a047c6a50ec80c3890dd623b85e237f0d1fd","status":"affected","version":"201e4aca5aa179e6c69a4dcd36a3562e56b8d670","versionType":"git"},{"lessThan":"cff0ef043e16feb5a02307c8f9d0117a96c5587c","status":"affected","version":"201e4aca5aa179e6c69a4dcd36a3562e56b8d670","versionType":"git"},{"lessThan":"9a6fc69a570c0780834246d52c856cc3dbc2605f","status":"affected","version":"201e4aca5aa179e6c69a4dcd36a3562e56b8d670","versionType":"git"},{"lessThan":"4f73486ca822305c1cf5b8ebc0b53a6ab3801a81","status":"affected","version":"201e4aca5aa179e6c69a4dcd36a3562e56b8d670","versionType":"git"},{"lessThan":"7cfe964e61c0ab667abd5f5b68e0acbf783efa4f","status":"affected","version":"201e4aca5aa179e6c69a4dcd36a3562e56b8d670","versionType":"git"},{"lessThan":"5669645c052f235726a85f443769b6fc02f66762","status":"affected","version":"201e4aca5aa179e6c69a4dcd36a3562e56b8d670","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/pstore/ram_core.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"3.5"},{"lessThan":"3.5","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"5.10.*","status":"unaffected","version":"5.10.252","versionType":"semver"},{"lessThanOrEqual":"5.15.*","status":"unaffected","version":"5.15.202","versionType":"semver"},{"lessThanOrEqual":"6.1.*","status":"unaffected","version":"6.1.165","versionType":"semver"},{"lessThanOrEqual":"6.6.*","status":"unaffected","version":"6.6.128","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.75","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.14","versionType":"semver"},{"lessThanOrEqual":"6.19.*","status":"unaffected","version":"6.19.4","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.0","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"5.10.252","versionStartIncluding":"3.5","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"5.15.202","versionStartIncluding":"3.5","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.1.165","versionStartIncluding":"3.5","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.6.128","versionStartIncluding":"3.5","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.75","versionStartIncluding":"3.5","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.14","versionStartIncluding":"3.5","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.19.4","versionStartIncluding":"3.5","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0","versionStartIncluding":"3.5","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\npstore/ram: fix buffer overflow in persistent_ram_save_old()\n\npersistent_ram_save_old() can be called multiple times for the same\npersistent_ram_zone (e.g., via ramoops_pstore_read -> ramoops_get_next_prz\nfor PSTORE_TYPE_DMESG records).\n\nCurrently, the function only allocates prz->old_log when it is NULL,\nbut it unconditionally updates prz->old_log_size to the current buffer\nsize and then performs memcpy_fromio() using this new size. If the\nbuffer size has grown since the first allocation (which can happen\nacross different kernel boot cycles), this leads to:\n\n1. A heap buffer overflow (OOB write) in the memcpy_fromio() calls\n2. A subsequent OOB read when ramoops_pstore_read() accesses the buffer\n   using the incorrect (larger) old_log_size\n\nThe KASAN splat would look similar to:\n  BUG: KASAN: slab-out-of-bounds in ramoops_pstore_read+0x...\n  Read of size N at addr ... by task ...\n\nThe conditions are likely extremely hard to hit:\n\n  0. Crash with a ramoops write of less-than-record-max-size bytes.\n  1. Reboot: ramoops registers, pstore_get_records(0) reads old crash,\n     allocates old_log with size X\n  2. Crash handler registered, timer started (if pstore_update_ms >= 0)\n  3. Oops happens (non-fatal, system continues)\n  4. pstore_dump() writes oops via ramoops_pstore_write() size Y (>X)\n  5. pstore_new_entry = 1, pstore_timer_kick() called\n  6. System continues running (not a panic oops)\n  7. Timer fires after pstore_update_ms milliseconds\n  8. pstore_timefunc() → schedule_work() → pstore_dowork() → pstore_get_records(1)\n  9. ramoops_get_next_prz() → persistent_ram_save_old()\n 10. buffer_size() returns Y, but old_log is X bytes\n 11. Y > X: memcpy_fromio() overflows heap\n\n  Requirements:\n  - a prior crash record exists that did not fill the record size\n    (almost impossible since the crash handler writes as much as it\n    can possibly fit into the record, capped by max record size and\n    the kmsg buffer almost always exceeds the max record size)\n  - pstore_update_ms >= 0 (disabled by default)\n  - Non-fatal oops (system survives)\n\nFree and reallocate the buffer when the new size differs from the\npreviously allocated size. This ensures old_log always has sufficient\nspace for the data being copied."}],"providerMetadata":{"dateUpdated":"2026-06-03T15:49:49.864Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/58bda5a1d1ee98254383ef34f76b2c35140513ea"},{"url":"https://git.kernel.org/stable/c/06d2c8bd108cea503f6f6e13e47495ed1085275f"},{"url":"https://git.kernel.org/stable/c/2fa9a047c6a50ec80c3890dd623b85e237f0d1fd"},{"url":"https://git.kernel.org/stable/c/cff0ef043e16feb5a02307c8f9d0117a96c5587c"},{"url":"https://git.kernel.org/stable/c/9a6fc69a570c0780834246d52c856cc3dbc2605f"},{"url":"https://git.kernel.org/stable/c/4f73486ca822305c1cf5b8ebc0b53a6ab3801a81"},{"url":"https://git.kernel.org/stable/c/7cfe964e61c0ab667abd5f5b68e0acbf783efa4f"},{"url":"https://git.kernel.org/stable/c/5669645c052f235726a85f443769b6fc02f66762"}],"title":"pstore/ram: fix buffer overflow in persistent_ram_save_old()","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-46253","datePublished":"2026-06-03T15:49:49.864Z","dateReserved":"2026-05-13T15:03:33.107Z","dateUpdated":"2026-06-03T15:49:49.864Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-06-03 18:16:26","lastModifiedDate":"2026-06-03 18:16:26","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"46253","Ordinal":"1","Title":"pstore/ram: fix buffer overflow in persistent_ram_save_old()","CVE":"CVE-2026-46253","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"46253","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\npstore/ram: fix buffer overflow in persistent_ram_save_old()\n\npersistent_ram_save_old() can be called multiple times for the same\npersistent_ram_zone (e.g., via ramoops_pstore_read -> ramoops_get_next_prz\nfor PSTORE_TYPE_DMESG records).\n\nCurrently, the function only allocates prz->old_log when it is NULL,\nbut it unconditionally updates prz->old_log_size to the current buffer\nsize and then performs memcpy_fromio() using this new size. If the\nbuffer size has grown since the first allocation (which can happen\nacross different kernel boot cycles), this leads to:\n\n1. A heap buffer overflow (OOB write) in the memcpy_fromio() calls\n2. A subsequent OOB read when ramoops_pstore_read() accesses the buffer\n   using the incorrect (larger) old_log_size\n\nThe KASAN splat would look similar to:\n  BUG: KASAN: slab-out-of-bounds in ramoops_pstore_read+0x...\n  Read of size N at addr ... by task ...\n\nThe conditions are likely extremely hard to hit:\n\n  0. Crash with a ramoops write of less-than-record-max-size bytes.\n  1. Reboot: ramoops registers, pstore_get_records(0) reads old crash,\n     allocates old_log with size X\n  2. Crash handler registered, timer started (if pstore_update_ms >= 0)\n  3. Oops happens (non-fatal, system continues)\n  4. pstore_dump() writes oops via ramoops_pstore_write() size Y (>X)\n  5. pstore_new_entry = 1, pstore_timer_kick() called\n  6. System continues running (not a panic oops)\n  7. Timer fires after pstore_update_ms milliseconds\n  8. pstore_timefunc() → schedule_work() → pstore_dowork() → pstore_get_records(1)\n  9. ramoops_get_next_prz() → persistent_ram_save_old()\n 10. buffer_size() returns Y, but old_log is X bytes\n 11. Y > X: memcpy_fromio() overflows heap\n\n  Requirements:\n  - a prior crash record exists that did not fill the record size\n    (almost impossible since the crash handler writes as much as it\n    can possibly fit into the record, capped by max record size and\n    the kmsg buffer almost always exceeds the max record size)\n  - pstore_update_ms >= 0 (disabled by default)\n  - Non-fatal oops (system survives)\n\nFree and reallocate the buffer when the new size differs from the\npreviously allocated size. This ensures old_log always has sufficient\nspace for the data being copied.","Type":"Description","Title":"pstore/ram: fix buffer overflow in persistent_ram_save_old()"}]}}}