CVE-2023-52840 is a use-after-free vulnerability in the Linux kernel Synaptics RMI4 input driver. In rmi_unregister_function(), put_device() may invoke rmi_release_function() and free the function object before subsequent code dereferences its num_of_irqs member. The upstream correction defers put_device() until after all accesses to the object have completed.
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 Synaptics RMI4 input-driver use-after-free flaw.
Linux kernel Synaptics RMI4 input-driver use-after-free vulnerability in rmi_unregister_function().
A low-impact use-after-free vulnerability in the Linux kernel Synaptics RMI4 input driver, occurring in rmi_unregister_function().
A use-after-free vulnerability in the Linux kernel Synaptics RMI4 input driver, within rmi_unregister_function(). Calling put_device() frees the function object before a subsequent dereference of fn->num_of_irqs; the fix moves put_device() to the end.
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.