Loading vulnerability…
CVE-2023-52492 is a NULL pointer dereference in the Linux kernel dmaengine subsystem. DMA channel registration can fail in __dma_async_device_channel_register(), which frees and clears the channel's per-CPU local state. Subsequent invocation of dma_async_device_unregister() unconditionally attempts channel unregistration through __dma_async_device_channel_unregister(). Without verifying that the local state remains allocated, this path can pass an invalid channel device state to device unregistration and dereference a NULL pointer. The upstream fix adds a NULL check in __dma_async_device_channel_unregister(), consistent with the registration error path.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A NULL-pointer issue in the Linux kernel DMA engine channel-unregistration function.
Linux kernel DMA engine NULL-pointer issue during channel unregistration.
Linux kernel DMA engine NULL-pointer flaw during channel unregistration.
Linux kernel DMA engine NULL-pointer issue during channel unregistration.
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.