Loading vulnerability…
CVE-2023-52522 is a race-condition flaw in the Linux kernel network neighbor subsystem's neigh_periodic_work() function. When deleting an RCU-protected list item, the writer did not use rcu_assign_pointer() or WRITE_ONCE() even though concurrent readers dereference the neighbor pointer with rcu_dereference(). The unprotected write can be torn, allowing a concurrent reader to observe an inconsistent value. The upstream correction uses rcu_assign_pointer() when deleting the RCU-protected item.
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.
14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel networking flaw involving possible store tearing when deleting an RCU-protected neighbor entry in neigh_periodic_work(). The fix uses rcu_assign_pointer() to safely publish the pointer update.
A locally exploitable, low-complexity vulnerability requiring low privileges that can cause high impact to availability; the content provides no further technical flaw description.
Linux kernel networking store-tearing race vulnerability.
Linux kernel neighbor-cache periodic-work store-tearing vulnerability.
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.