Linux kernel sk_psock_get refcount bug due to sk_user_data type confusion
CVE-2022-49979 is a Linux kernel networking flaw in the interaction between SMC fallback handling and psock lookup logic. During the SMC fallback process in connect(), the kernel may replace TCP with SMC and set clcsk->sk_user_data to reference the original SMC socket in smc_fback_replace_callbacks() so wakeups can be forwarded after fallback. Later, during shutdown(), sk_psock_get() may be called and incorrectly interpret that same sk_user_data field as a psock pointer. Because both SMC and psock reuse sk_user_data, the field can be misclassified, leading sk_psock_get() to operate on an object of the wrong type and trigger refcount corruption warnings such as refcount saturation and memory leakage. The fix introduces an explicit SK_USER_DATA_PSOCK tag bit in the PTRMASK scheme so the kernel can distinguish whether sk_user_data actually points to a psock object before taking a reference.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
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.
Recent activity
3 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.
The version that knows your environment.
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.