NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizes
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 37f2d2cd8eadddbbd9c7bda327a9393399b2f89b, Kernel 72c14aed6838b5d90b4dd926b6a339b34bb02e08, Kernel a231ae6bb50e7c0a9e9efd7b0d10687f1d71b3a3 and 2 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =2.6.12, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <37f2d2cd8eadddbbd9c7bda327a9393399b2f89b, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <72c14aed6838b5d90b4dd926b6a339b34bb02e08, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a231ae6bb50e7c0a9e9efd7b0d10687f1d71b3a3, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a648fdeb7c0e17177a2280344d015dba3fbe3314, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <aa9051ddb4b378bd22e72a67bc77b9fc1482c5f0 | 37f2d2cd8eadddbbd9c7bda327a9393399b2f89b, 72c14aed6838b5d90b4dd926b6a339b34bb02e08, a231ae6bb50e7c0a9e9efd7b0d10687f1d71b3a3, a648fdeb7c0e17177a2280344d015dba3fbe3314, aa9051ddb4b378bd22e72a67bc77b9fc1482c5f0 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket