CVE-2022-48829: NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizes
In the Linux kernel, the following vulnerability has been resolved:
NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizes
iattr::ia_size is a loff_t, so these NFSv3 procedures must be
careful to deal with incoming client size values that are larger
than s64_max without corrupting the value.
Silently capping the value results in storing a different value
than the client passed in which is unexpected behavior, so remove
the min_t() check in decode_sattr3().
Note that RFC 1813 permits only the WRITE procedure to return
NFS3ERR_FBIG. We believe that NFSv3 reference implementations
also return NFS3ERR_FBIG when ia_size is too large.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue affects the NFS server’s handling of very large file sizes in NFSv3 CREATE and SETATTR requests. The main business concern is unexpected file-size handling on systems serving NFSv3, not confirmed remote code execution or active exploitation.
Executive priority
Prioritize review for business-critical Linux NFS servers and affected vendor appliances. Without evidence of active exploitation or a severity score, this is best handled through controlled kernel patching and exposure reduction rather than emergency response.
Technical view
NFSD decoded NFSv3 size attributes into loff_t and previously capped oversized client values, risking corrupted or unexpected size semantics. Kernel stable commits remove that capping so oversized values can be handled consistently with NFSv3 error behavior expectations.
Likely exposure
Exposure is most likely on Linux systems running the kernel NFS server with NFSv3 enabled and reachable by clients. Systems not serving NFS, or not allowing NFSv3 access, are unlikely to be exposed based on the provided sources.
Exploitation context
The bundle does not show CISA KEV listing, public exploitation, exploit tooling, or CVSS scoring. Treat exploitation status as unconfirmed. The available evidence supports a protocol edge-case handling flaw in NFSD rather than a confirmed widespread attack path.
Researcher notes
Key review areas are fs/nfsd NFSv3 SETATTR and CREATE size decoding paths, especially handling values above signed 64-bit limits. Evidence is limited to CVE metadata, kernel stable commits, and vendor advisories; impact details remain incomplete.
Mitigation direction
Apply vendor or distribution kernel updates containing the referenced stable NFSD fixes.
Review vendor advisories, including Siemens notices, if using affected embedded or industrial products.
Restrict NFS service exposure to trusted networks and authenticated clients.
Disable NFSv3 where it is not required operationally.
Validation and detection
Inventory Linux hosts running kernel NFS server services.
Confirm whether NFSv3 is enabled and reachable from client networks.
Compare running kernel packages against vendor-fixed kernel advisories.
Check whether appliances map to the Siemens affected-product advisories.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-48829 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.