CVE-2025-21796 is a use-after-free flaw in the Linux kernel NFS server (nfsd) ACL handling path. If retrieval of a default POSIX ACL fails, the failure path releases the ACL objects but leaves acl_access referencing a released POSIX ACL. Subsequent cleanup in nfs3svc_release_getacl can release or reference the stale object again, producing a reference-count underflow and use-after-free warning. The fix clears both ACL pointers after releasing them.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel NFSD ACL resource-lifetime flaw.
A Linux kernel NFS server (nfsd) use-after-free/refcount-underflow vulnerability caused by stale ACL pointers after posix_acl_release. It can result in a kernel warning and potentially a kernel panic/denial of service.
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.