{"uuid": "7bd564df-88b1-4420-b6cd-c07e2e24f8d8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2022-49927", "type": "seen", "source": "https://t.me/cvedetector/24243", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2022-49927 - Linux NFS kmemleak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2022-49927 \nPublished : May 1, 2025, 3:16 p.m. | 1\u00a0hour, 9\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnfs4: Fix kmemleak when allocate slot failed  \n  \nIf one of the slot allocate failed, should cleanup all the other  \nallocated slots, otherwise, the allocated slots will leak:  \n  \n  unreferenced object 0xffff8881115aa100 (size 64):  \n    comm \"\"mount.nfs\"\", pid 679, jiffies 4294744957 (age 115.037s)  \n    hex dump (first 32 bytes):  \n      00 cc 19 73 81 88 ff ff 00 a0 5a 11 81 88 ff ff  ...s......Z.....  \n      00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................  \n    backtrace:  \n      [<000000007a4c434a] nfs4_find_or_create_slot+0x8e/0x130  \n      [<000000005472a39c] nfs4_realloc_slot_table+0x23f/0x270  \n      [<00000000cd8ca0eb] nfs40_init_client+0x4a/0x90  \n      [<00000000128486db] nfs4_init_client+0xce/0x270  \n      [<000000008d2cacad] nfs4_set_client+0x1a2/0x2b0  \n      [<000000000e593b52] nfs4_create_server+0x300/0x5f0  \n      [<00000000e4425dd2] nfs4_try_get_tree+0x65/0x110  \n      [<00000000d3a6176f] vfs_get_tree+0x41/0xf0  \n      [<0000000016b5ad4c] path_mount+0x9b3/0xdd0  \n      [<00000000494cae71] __x64_sys_mount+0x190/0x1d0  \n      [<000000005d56bdec] do_syscall_64+0x35/0x80  \n      [<00000000687c9ae4] entry_SYSCALL_64_after_hwframe+0x46/0xb0 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"01 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-01T19:01:34.000000Z"}