Loading vulnerability…
CVE-2022-48827 is an integer-overflow-related flaw in the Linux kernel NFS server (NFSD) handling of READ requests near the maximum signed file offset. A client-side aligned-buffer behavior can round a requested read length upward to the server read size. For a sufficiently large file and an offset close to OFFSET_MAX, the resulting range overflows the server's internal loff_t calculations. NFSD returns NFSERR_INVAL, a status that Linux NFS clients may retry indefinitely. The fix makes out-of-range READ requests return a short successful result with EOF set, and explicitly validates/converts NFSv3 and NFSv4 wire-format u64 offsets to loff_t before internal use so VFS maximum-file-size checks are applied correctly.
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 involving READ request handling near OFFSET_MAX.
A Linux kernel NFSD flaw affecting READ behavior near OFFSET_MAX, fixed in the Red Hat kernel-rt update.
A Linux kernel NFSD flaw affecting handling of READ operations near OFFSET_MAX.
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.