CVE-2023-52450 is a NULL pointer dereference in the Linux kernel perf x86 Intel uncore subsystem. Intel UPI topology discovery used a physical socket identifier where a logical socket identifier was required. The resulting invalid topology-array index can access an out-of-bounds entry and leave the UPI topology pointer NULL, which is subsequently dereferenced by upi_fill_topology().
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
NULL-pointer dereference in Linux kernel Intel topology handling.
NULL-pointer dereference in the Linux kernel Intel topology handling code.
A Linux kernel perf/x86 Intel uncore topology-discovery flaw where use of a physical rather than logical socket ID can cause an out-of-bounds topology-array access and subsequent NULL-pointer dereference in upi_fill_topology().
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.