CVE-2023-52749 is a race condition in the Linux kernel SPI subsystem's suspend and resume handling. A synchronous no-queue SPI transfer sets the controller's current-message pointer and begins processing. If system suspend interrupts that transfer, resume processing can restart the SPI queue and clear the current-message pointer before the interrupted transfer resumes. When the transfer later finalizes, it dereferences the now-NULL pointer. The upstream fix serializes suspend against synchronous transfers by acquiring the SPI bus mutex and maintaining a suspend flag.
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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel SPI null-pointer dereference during suspend handling.
Linux kernel SPI null-pointer dereference during system suspend.
A Linux kernel SPI subsystem null-pointer dereference vulnerability during suspend.
A CVE included in the OpenShift Container Platform 4.15.40 advisory; no vulnerability details are provided in the 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.