In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
Inthe Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In theLinux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handlingof large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linuxkernel, the following vulnerability has beenresolved:NFSD: Fix NFSv3SETATTR/CREATE's handling oflarge file sizesiattr::ia_sizeis a loff_t,so these NFSv3 proceduresmustbecareful to deal with incoming client size values that are largerthan s64_max without corrupting thevalue.Silently capping the value resultsin storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t()check in decode_sattr3().Note that RFC 1813 permits only the WRITEprocedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.The Linux kernel CVE team has assigned CVE-2022-48829 to this issue.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
IntheLinuxkernel,thefollowingvulnerability hasbeen resolved:NFSD: Fix NFSv3 SETATTR/CREATEs handling of large filesizesiattr::ia_size is a loff_t,so these NFSv3 procedures mustbecareful todeal with incoming clientsizevalues that arelargerthan s64_max without corrupting the value.Silently capping the value results instoring a different valuethan the clientpassed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813permits only the WRITE procedure to returnNFS3ERR_FBIG. We believethat NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE shandling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATEs handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE shandling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATEs handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE shandling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATEs handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE shandling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATEs handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE shandling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATEs handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE shandling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATEs handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE shandling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATEs handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE shandling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATEs handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE shandling of large file sizesiattr::ia_size is aloff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing adifferent valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATE s handling of large file sizesiattr::ia_size is a loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storing a different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
| linux | | https://git.kernel.org/linus/a648fdeb7c0e17177a2280344d015dba3fbe3314 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:NFSD: Fix NFSv3 SETATTR/CREATEs handling of large file sizesiattr::ia_size isa loff_t, so these NFSv3 procedures must becareful to deal with incoming client size values that are largerthan s64_max without corrupting the value.Silently capping the value results in storinga different valuethan the client passed in which is unexpected behavior, so removethe min_t() check in decode_sattr3().Note that RFC 1813 permits only the WRITE procedure to returnNFS3ERR_FBIG. We believe that NFSv3 reference implementationsalso return NFS3ERR_FBIG when ia_size is too large.
