Loading vulnerability…
CVE-2022-48816 is a race condition in the Linux kernel SUNRPC subsystem. During sysfs reads, the transport object's ->sock pointer can be changed asynchronously and set to NULL unless ->recv_mutex is held. If sysfs code accesses ->sock without holding that mutex, a concurrent change can occur and trigger a kernel oops due to unsafe access to the socket pointer. The issue description notes that commit 17f09d3f619a ("SUNRPC: Check if the xprt is connected before handling sysfs reads") only narrowed the race window rather than eliminating it; the proper fix is to lock against ->sock changing during sysfs reads by holding ->recv_mutex.
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.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.