{"uuid": "32ffb80b-091d-4ce6-a0ad-068d3cf6fbb7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48829", "type": "seen", "source": "https://t.me/cvedetector/936", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2022-48829 - NFS on Linux Kernel Large File Size Handling Buffer Overflow\", \n  \"Content\": \"CVE ID : CVE-2022-48829 \nPublished : July 16, 2024, 12:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nNFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizes  \n  \niattr::ia_size is a loff_t, so these NFSv3 procedures must be  \ncareful to deal with incoming client size values that are larger  \nthan s64_max without corrupting the value.  \n  \nSilently capping the value results in storing a different value  \nthan the client passed in which is unexpected behavior, so remove  \nthe min_t() check in decode_sattr3().  \n  \nNote that RFC 1813 permits only the WRITE procedure to return  \nNFS3ERR_FBIG. We believe that NFSv3 reference implementations  \nalso return NFS3ERR_FBIG when ia_size is too large. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"16 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-16T15:26:20.000000Z"}