CVE-2023-1637 is a flaw in Linux kernel x86 CPU power-management handling of suspend-to-RAM (S3) resume. The kernel did not save and restore speculative-execution model-specific registers (MSRs) during the S3 suspend/resume sequence, leaving the boot CPU susceptible to speculative-execution-based memory disclosure. The issue is classified as CWE-908, Use of Uninitialized Resource.
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.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel flaw involving saving and restoring speculative model-specific registers (MSRs) during S3 suspend and resume.
A vulnerability addressed by the Red Hat Enterprise Linux 8 kernel security advisory; no further technical details are provided in the content.
A Linux kernel issue involving failure to save and restore speculative model-specific registers during S3 suspend and resume.
A Linux kernel vulnerability addressed by the Red Hat kernel-rt update; no further technical description is provided in the advisory content.
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.