| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2022-48829: NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizes |
| |
| Description |
| =========== |
| |
| 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. |
| |
| The Linux kernel CVE team has assigned CVE-2022-48829 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 5.10.220 with commit a231ae6bb50e7c0a9e9efd7b0d10687f1d71b3a3 |
| Fixed in 5.15.24 with commit 37f2d2cd8eadddbbd9c7bda327a9393399b2f89b |
| Fixed in 5.16.10 with commit aa9051ddb4b378bd22e72a67bc77b9fc1482c5f0 |
| Fixed in 5.17 with commit a648fdeb7c0e17177a2280344d015dba3fbe3314 |
| |
| Please see https://www.kernel.org for a full list of currently supported |
| kernel versions by the kernel community. |
| |
| Unaffected versions might change over time as fixes are backported to |
| older supported kernel versions. The official CVE entry at |
| https://cve.org/CVERecord/?id=CVE-2022-48829 |
| will be updated if fixes are backported, please check that for the most |
| up to date information about this issue. |
| |
| |
| Affected files |
| ============== |
| |
| The file(s) affected by this issue are: |
| fs/nfsd/nfs3xdr.c |
| |
| |
| Mitigation |
| ========== |
| |
| The Linux kernel CVE team recommends that you update to the latest |
| stable kernel version for this, and many other bugfixes. Individual |
| changes are never tested alone, but rather are part of a larger kernel |
| release. Cherry-picking individual commits is not recommended or |
| supported by the Linux kernel community at all. If however, updating to |
| the latest release is impossible, the individual changes to resolve this |
| issue can be found at these commits: |
| https://git.kernel.org/stable/c/a231ae6bb50e7c0a9e9efd7b0d10687f1d71b3a3 |
| https://git.kernel.org/stable/c/37f2d2cd8eadddbbd9c7bda327a9393399b2f89b |
| https://git.kernel.org/stable/c/aa9051ddb4b378bd22e72a67bc77b9fc1482c5f0 |
| https://git.kernel.org/stable/c/a648fdeb7c0e17177a2280344d015dba3fbe3314 |
