Loading vulnerability…
CVE-2022-48829 affects the Linux kernel NFS server (NFSD) handling of NFSv3 SETATTR and CREATE requests carrying a file-size value greater than the maximum signed 64-bit value. The affected decoding logic capped the incoming unsigned size at the signed maximum before assigning it to iattr::ia_size, a loff_t. This changed the client-supplied value to a valid maximum size rather than allowing subsequent validation to reject the unrepresentable value. The fix removes the premature cap so oversized values are identified as invalid and rejected with NFS3ERR_FBIG.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel NFSD vulnerability in NFSv3 SETATTR and CREATE handling of large file sizes.
A Linux kernel NFSD flaw in NFSv3 SETATTR and CREATE handling of large file sizes.
A Linux kernel NFSD flaw in NFSv3 SETATTR and CREATE handling of large file sizes.
A Linux kernel NFSD vulnerability involving NFSv3 SETATTR and CREATE handling of large file sizes, fixed in the Red Hat kernel-rt update.
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.