{"vulnerability": "CVE-2024-50254", "sightings": [{"uuid": "52a7c5e2-e7d0-4383-8e0c-1fe35f21abe1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-50254", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113453077695714662", "content": "", "creation_timestamp": "2024-11-09T12:49:41.432679Z"}, {"uuid": "5506c51b-2c89-49f7-93f1-7eb1810544f3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-50254", "type": "seen", "source": "https://t.me/cvedetector/10320", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50254 - Linux Kernel bpf Memory Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-50254 \nPublished : Nov. 9, 2024, 11:15 a.m. | 40\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbpf: Free dynamically allocated bits in bpf_iter_bits_destroy()  \n  \nbpf_iter_bits_destroy() uses \"kit->nr_bits <=<00000000c452b4ab] kmemleak_alloc+0x4b/0x80  \n [<0000000004e09f80] __kmalloc_node_noprof+0x480/0x5c0  \n [<00000000597124d6] __alloc.isra.0+0x89/0xb0  \n [<000000004ebfffcd] alloc_bulk+0x2af/0x720  \n [<00000000d9c10145] prefill_mem_cache+0x7f/0xb0  \n [<00000000ff9738ff] bpf_mem_alloc_init+0x3e2/0x610  \n [<000000008b616eac] bpf_global_ma_init+0x19/0x30  \n [<00000000fc473efc] do_one_initcall+0xd3/0x3c0  \n [<00000000ec81498c] kernel_init_freeable+0x66a/0x940  \n [<00000000b119f72f] kernel_init+0x20/0x160  \n [<00000000f11ac9a7] ret_from_fork+0x3c/0x70  \n [<0000000004671da4] ret_from_fork_asm+0x1a/0x30  \n  \nThat is because nr_bits will be set as zero in bpf_iter_bits_next()  \nafter all bits have been iterated.  \n  \nFix the issue by setting kit->bit to kit->nr_bits instead of setting  \nkit->nr_bits to zero when the iteration completes in  \nbpf_iter_bits_next(). In addition, use \"!nr_bits || bits >= nr_bits\" to  \ncheck whether the iteration is complete and still use \"nr_bits > 64\" to  \nindicate whether bits are dynamically allocated. The \"!nr_bits\" check is  \nnecessary because bpf_iter_bits_new() may fail before setting  \nkit->nr_bits, and this condition will stop the iteration early instead  \nof accessing the zeroed or freed kit->bits.  \n  \nConsidering the initial value of kit->bits is -1 and the type of  \nkit->nr_bits is unsigned int, change the type of kit->nr_bits to int.  \nThe potential overflow problem will be handled in the following patch. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-09T13:17:41.000000Z"}]}