Loading vulnerability…
CVE-2025-39697 is a race condition in the Linux kernel NFS client write path when updating an existing write request. nfs_lock_and_join_requests() verifies that a request remains attached to its mapping before acquiring the page-group lock, allowing a concurrent nfs_inode_remove_request() operation to remove the request during that interval. This creates a use-after-free condition. The upstream correction acquires the page-group lock earlier in nfs_lock_and_join_requests() and retains it across request removal.
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.
33 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel NFS race condition when updating an existing write.
A Linux kernel NFS race condition vulnerability when updating an existing write.
A race condition in the Linux kernel NFS subsystem when updating an existing write.
A Linux kernel NFS race condition when updating an existing write, addressed by the Red Hat kernel-rt update for Red Hat Enterprise Linux 8.
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.