NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizes
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.4.295, 5.10.220, 5.15.24, 5.16.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 72c14aed6838b5d90b4dd926b6a339b34bb02e08; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in a231ae6bb50e7c0a9e9efd7b0d10687f1d71b3a3; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 37f2d2cd8eadddbbd9c7bda327a9393399b2f89b; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in aa9051ddb4b378bd22e72a67bc77b9fc1482c5f0; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in a648fdeb7c0e17177a2280344d015dba3fbe3314
- Linux Linux
2.6.12
- KernelLinux
From 2.6.12 · fixed in 5.4.295; From 5.5.0 · fixed in 5.10.220; From 5.11.0 · fixed in 5.15.24; From 5.16.0 · fixed in 5.16.10