Loading vulnerability…
CVE-2025-38724 is a race condition in the Linux kernel NFS server daemon (nfsd) NFSv4 client-identifier confirmation path. nfsd4_setclientid_confirm() failed to handle failure from get_client_locked() when a SETCLIENTID_CONFIRM request raced with expiration of an existing confirmed client. The failed reference acquisition could subsequently result in use of a freed client object. The upstream fix acquires the client reference earlier for an extant confirmed client, treats unsuccessful acquisition as no confirmed client being present, and fails the operation when the unconfirmed client is expiring.
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.
22 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel NFSD vulnerability in nfsd4_setclientid_confirm() related to handling get_client_locked() failure.
A Linux kernel NFSD vulnerability involving failure handling in nfsd4_setclientid_confirm().
A Linux kernel NFSD vulnerability involving failure handling in nfsd4_setclientid_confirm().
A Linux kernel vulnerability in nfsd involving failure handling in nfsd4_setclientid_confirm().
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.