{"uuid": "6fa8677d-f156-4be9-9f46-76e46eb11f01", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48829", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/19693", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2022-48829\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: 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.\n\ud83d\udccf Published: 2024-07-16T11:44:13.313Z\n\ud83d\udccf Modified: 2025-06-27T10:21:09.814Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/72c14aed6838b5d90b4dd926b6a339b34bb02e08\n2. https://git.kernel.org/stable/c/a231ae6bb50e7c0a9e9efd7b0d10687f1d71b3a3\n3. https://git.kernel.org/stable/c/37f2d2cd8eadddbbd9c7bda327a9393399b2f89b\n4. https://git.kernel.org/stable/c/aa9051ddb4b378bd22e72a67bc77b9fc1482c5f0\n5. https://git.kernel.org/stable/c/a648fdeb7c0e17177a2280344d015dba3fbe3314", "creation_timestamp": "2025-06-27T10:49:58.000000Z"}