Loading vulnerability…
CVE-2023-52817 is a NULL pointer dereference in the Linux kernel DRM AMDGPU driver's SMC-register debugfs read handler, amdgpu_debugfs_regs_smc_read. On certain AMD GPU models, including Vega 20, the handler can attempt to call through the smc_rreg pointer when that pointer is NULL. Reading the affected AMDGPU SMC-register debugfs interface consequently causes a kernel-mode fault.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel AMDGPU NULL-pointer dereference flaw.
A moderate-severity Linux kernel DRM/AMD GPU (amdgpu) null-pointer-access vulnerability triggered when the smc_rreg pointer is NULL. It was fixed in multiple upstream kernel versions and addressed through Red Hat Enterprise Linux 8 and 9 errata.
A moderate-severity Linux kernel AMDGPU driver NULL-pointer dereference in the debugfs SMC-register read path. A local low-privileged user able to read the affected debugfs file can crash the kernel, causing denial of service.
A Linux kernel AMDGPU debugfs null-pointer dereference affecting the amdgpu_regs_smc interface. A local user able to read the relevant debugfs file can trigger a kernel crash/denial of service on affected hardware.
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.