Use-after-free in Linux kernel NFSD /proc/fs/nfs/exports handling
CVE-2026-31403 is a use-after-free vulnerability in the Linux kernel NFSD subsystem involving the /proc/fs/nfs/exports proc entry. The proc entry is created at module initialization and persists for the lifetime of the module. In the vulnerable code path, exports_proc_open() captures the caller's current network namespace and stores that namespace's svc_export_cache in seq->private, but does not take a reference on the associated struct net. If that network namespace is later torn down, nfsd_net_exit() invokes nfsd_export_shutdown(), which frees the export cache. A process that still holds an open file descriptor for /proc/fs/nfs/exports can then perform subsequent reads that dereference the freed cache_detail structure and walk a freed hash table. The fix is to hold a reference to the network namespace for the lifetime of the open exports file descriptor and release it in exports_release(), using the cache_detail net pointer already stored in cd->net.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
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.
Recent activity
5 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
The version that knows your environment.
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.