{"vulnerability": "CVE-2022-48924", "sightings": [{"uuid": "f3df837e-5cf1-4b47-bf2e-c4ea588f495d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2022-48924", "type": "seen", "source": "https://t.me/cvedetector/3850", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2022-48924 - Intel int3400_thermal Memory Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2022-48924 \nPublished : Aug. 22, 2024, 2:15 a.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nthermal: int340x: fix memory leak in int3400_notify()  \n  \nIt is easy to hit the below memory leaks in my TigerLake platform:  \n  \nunreferenced object 0xffff927c8b91dbc0 (size 32):  \n  comm \"kworker/0:2\", pid 112, jiffies 4294893323 (age 83.604s)  \n  hex dump (first 32 bytes):  \n    4e 41 4d 45 3d 49 4e 54 33 34 30 30 20 54 68 65  NAME=INT3400 The  \n    72 6d 61 6c 00 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b a5  rmal.kkkkkkkkkk.  \n  backtrace:  \n    [] __kmalloc_track_caller+0x2fe/0x4a0  \n    [] kvasprintf+0x65/0xd0  \n    [] kasprintf+0x4e/0x70  \n    [] int3400_notify+0x82/0x120 [int3400_thermal]  \n    [] acpi_ev_notify_dispatch+0x54/0x71  \n    [] acpi_os_execute_deferred+0x17/0x30  \n    [] process_one_work+0x21a/0x3f0  \n    [] worker_thread+0x4a/0x3b0  \n    [] kthread+0xfd/0x130  \n    [] ret_from_fork+0x1f/0x30  \n  \nFix it by calling kfree() accordingly. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"22 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-22T05:07:50.000000Z"}]}