Loading vulnerability…
CVE-2023-53401 is a race condition in the Linux kernel memory-control-group kmem accounting path. In obj_stock_flush_required(), the cached object cgroup pointer can be reset after it is checked but before it is dereferenced, resulting in a NULL-pointer dereference. The concurrent operations observed involve object-stock draining/refilling and memory-cgroup charging. The upstream correction makes all accesses to the cached object cgroup pointer use READ_ONCE() and WRITE_ONCE() primitives.
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.
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel memory-management NULL pointer dereference in obj_stock_flush_required().
A NULL-pointer dereference vulnerability in the Linux kernel memory-management kmem obj_stock_flush_required function.
A NULL-pointer dereference vulnerability in the Linux kernel memory-management kmem code, specifically obj_stock_flush_required(), addressed in the Red Hat kernel-rt update.
A Linux kernel memory-management flaw involving a NULL-pointer dereference in obj_stock_flush_required().
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.