Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-53331: pstore/ram: Check start of empty przs during init

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 25fb4e3402d46f425ec135ef6f09792a4c1b3003, 3.19, 4.10.

Low priority for now. Upgrade to Linux Linux 25fb4e3402d46f425ec135ef6f09792a4c1b3003, 3.19, 4.10 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: pstore/ram: Check start of empty przs during init After commit 30696378f68a ("pstore/ram: Do not treat empty buffers as valid"), initialization would assume a prz was valid after seeing that the buffer_size is zero (regardless of the buffer start position). This unchecked start value means it could be outside the bounds of the buffer, leading to future access panics when written to: sysdump_panic_event+0x3b4/0x5b8 atomic_notifier_call_chain+0x54/0x90 panic+0x1c8/0x42c die+0x29c/0x2a8 die_kernel_fault+0x68/0x78 __do_kernel_fault+0x1c4/0x1e0 do_bad_area+0x40/0x100 do_translation_fault+0x68/0x80 do_mem_abort+0x68/0xf8 el1_da+0x1c/0xc0 __raw_writeb+0x38/0x174 __memcpy_toio+0x40/0xac persistent_ram_update+0x44/0x12c persistent_ram_write+0x1a8/0x1b8 ramoops_pstore_write+0x198/0x1e8 pstore_console_write+0x94/0xe0 ... To avoid this, also check if the prz start is 0 during the initialization phase. If not, the next prz sanity check case will discover it (start > size) and zap the buffer back to a sane state. [kees: update commit log with backtrace and clarifications]

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Sep 16, 2025
Updated
Aug 5, 2026
EPSS
0.1% · 5th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
7.8
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-53331

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel3.18.133 and later · before 3.19
  • linux linux kernel4.4.172 and later · before 4.5
  • linux linux kernel4.9.153 and later · before 4.10
  • linux linux kernel4.14.96 and later · before 4.14.326
  • linux linux kernel4.19.18 and later · before 4.19.295
  • linux linux kernel4.20.5 and later · before 5.4.257
  • linux linux kernel5.5 and later · before 5.10.195
  • linux linux kernel5.11 and later · before 5.15.132
  • linux linux kernel5.16 and later · before 6.1.53
  • linux linux kernel6.2 and later · before 6.4.16
  • linux linux kernel6.5 and later · before 6.5.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • ec7f99261da9a20d63cbd273511a11a2efe698f2, f250e4c562a3bd106575032666e9ef46f31231f8, fffdbf586866e9500b53c9d4b061d3983720375a, 9e969ba431b46b1891c88cea36f722f3bfe8a180, 5.0affected
    • e1e3a46706bd4037e8b7407dc660ae6e05b8ac56 and later · before 89312657337e6e03ad6e9ea1a462bd9c158c85c8affected · git
    • 265242d82a3c6a8bd9120d06b4801f8d7ae9a346 and later · before c807ccdd812d18985860504b503899f3140a9549affected · git
    • 30696378f68a9e3dad6bfe55938b112e72af00c2 and later · before e972231db29b5d1dccc13bf9d5ba55b6979a69edaffected · git
    • 30696378f68a9e3dad6bfe55938b112e72af00c2 and later · before dc2f60de9a7d3efd982440117dab5579898d808caffected · git
    • 30696378f68a9e3dad6bfe55938b112e72af00c2 and later · before fedecaeef88899d940b69368c996e8b3b0b8650daffected · git
    • 30696378f68a9e3dad6bfe55938b112e72af00c2 and later · before e95d7a8a6edd14f8fab44c777dd7281db91f6ae2affected · git
    • 30696378f68a9e3dad6bfe55938b112e72af00c2 and later · before f77990358628b01bdc03752126ff5f716ea37615affected · git
    • 30696378f68a9e3dad6bfe55938b112e72af00c2 and later · before 25fb4e3402d46f425ec135ef6f09792a4c1b3003affected · git
    • 30696378f68a9e3dad6bfe55938b112e72af00c2 and later · before fe8c3623ab06603eb760444a032d426542212021affected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.55-16.1.55-1
Debian:13linuxbefore 6.5.3-16.5.3-1
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-570.58.1.el9_60:5.14.0-570.58.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-611.7.1.el9_70:5.14.0-611.7.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-develbefore 0:5.14.0-611.7.1.el9_70:5.14.0-611.7.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-develbefore 0:5.14.0-570.58.1.el9_60:5.14.0-570.58.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-570.58.1.el9_60:5.14.0-570.58.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-611.7.1.el9_70:5.14.0-611.7.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-64k-debuginfobefore 0:5.14.0-570.58.1.el9_60:5.14.0-570.58.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-64k-debuginfobefore 0:5.14.0-611.7.1.el9_70:5.14.0-611.7.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-64k-develbefore 0:5.14.0-611.7.1.el9_70:5.14.0-611.7.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-64k-develbefore 0:5.14.0-570.58.1.el9_60:5.14.0-570.58.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-64k-devel-matchedbefore 0:5.14.0-611.7.1.el9_70:5.14.0-611.7.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-64k-devel-matchedbefore 0:5.14.0-570.58.1.el9_60:5.14.0-570.58.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-debug-debuginfobefore 0:5.14.0-570.58.1.el9_60:5.14.0-570.58.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-debug-debuginfobefore 0:5.14.0-611.7.1.el9_70:5.14.0-611.7.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-debug-develbefore 0:5.14.0-611.7.1.el9_70:5.14.0-611.7.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-debug-develbefore 0:5.14.0-570.58.1.el9_60:5.14.0-570.58.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-570.58.1.el9_60:5.14.0-570.58.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-611.7.1.el9_70:5.14.0-611.7.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-debuginfobefore 0:5.14.0-570.58.1.el9_60:5.14.0-570.58.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-debuginfobefore 0:5.14.0-611.7.1.el9_70:5.14.0-611.7.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-611.7.1.el9_70:5.14.0-611.7.1.el9_7
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-570.58.1.el9_60:5.14.0-570.58.1.el9_6

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2023-53329Sep 16, 2025 · workqueue: fix data race with the pwq->stats[] increment
    18Monitor
  • ← EarlierCVE-2023-53330Sep 16, 2025 · caif: fix memory leak in cfctrl_linkup_request()
    22Monitor
  • Later →CVE-2023-53332Sep 16, 2025 · genirq/ipi: Fix NULL pointer deref in irq_data_get_affinity_mask()
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux25fb4e3402d46f425ec135ef6f09792a4c1b3003Vendor (CNA)
Linux Linux3.19Vendor (CNA)
Linux Linux4.10Vendor (CNA)
Linux Linux4.14.326Vendor (CNA)
Linux Linux4.19.295Vendor (CNA)
Linux Linux4.21Vendor (CNA)
Linux Linux4.5Vendor (CNA)
Linux Linux89312657337e6e03ad6e9ea1a462bd9c158c85c8Vendor (CNA)
Linux Linuxc807ccdd812d18985860504b503899f3140a9549Vendor (CNA)
Linux Linuxdc2f60de9a7d3efd982440117dab5579898d808cVendor (CNA)
Linux Linuxe95d7a8a6edd14f8fab44c777dd7281db91f6ae2Vendor (CNA)
Linux Linuxe972231db29b5d1dccc13bf9d5ba55b6979a69edVendor (CNA)
Linux Linuxf77990358628b01bdc03752126ff5f716ea37615Vendor (CNA)
Linux Linuxfe8c3623ab06603eb760444a032d426542212021Vendor (CNA)
Linux Linuxfedecaeef88899d940b69368c996e8b3b0b8650dVendor (CNA)
debian:linux6.1.55-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-570.58.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-570.58.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-570.58.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-570.58.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-570.58.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-570.58.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-570.58.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-570.58.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-570.58.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-570.58.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-570.58.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:5.14.0-570.58.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
rocky linux:kernel0:5.14.0-570.58.1.el9_6 · Rocky Linux:9Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-787 · Out-of-bounds Write

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records