Loading vulnerability…
CVE-2023-53331 is an out-of-bounds write vulnerability in the Linux kernel pstore/ram subsystem used by ramoops persistent-RAM zones. Following a change intended to reject empty buffers, initialization treated a zone with a zero buffer size as valid without validating that its start offset was zero. A nonzero start offset could therefore remain outside the zone bounds. Subsequent persistent-RAM writes, including pstore console logging during panic processing, could use that invalid offset and fault while writing. The fix validates that an empty zone has a zero start offset; invalid metadata is then rejected by the existing sanity checks and the zone is reset to a safe state.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel pstore/ram initialization flaw involving checking the start of empty persistent RAM zones.
Linux kernel pstore/ram initialization flaw involving the start of empty persistent RAM zones.
A Linux kernel pstore/ram initialization flaw involving validation of empty persistent RAM zones.
A Linux kernel pstore/ram initialization flaw addressed by checking the start of empty persistent RAM zones (przs).
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.