{"uuid": "b97ab942-8874-423b-9b2c-30228103e92d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-53156", "type": "seen", "source": "https://t.me/cvedetector/13597", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-53156 - \"Ath9k HTC Endpoint Bounds Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-53156 \nPublished : Dec. 24, 2024, 12:15 p.m. | 45\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nwifi: ath9k: add range check for conn_rsp_epid in htc_connect_service()  \n  \nI found the following bug in my fuzzer:  \n  \n  UBSAN: array-index-out-of-bounds in drivers/net/wireless/ath/ath9k/htc_hst.c:26:51  \n  index 255 is out of range for type 'htc_endpoint [22]'  \n  CPU: 0 UID: 0 PID: 8 Comm: kworker/0:0 Not tainted 6.11.0-rc6-dirty #14  \n  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014  \n  Workqueue: events request_firmware_work_func  \n  Call Trace:  \n     \n   dump_stack_lvl+0x180/0x1b0  \n   __ubsan_handle_out_of_bounds+0xd4/0x130  \n   htc_issue_send.constprop.0+0x20c/0x230  \n   ? _raw_spin_unlock_irqrestore+0x3c/0x70  \n   ath9k_wmi_cmd+0x41d/0x610  \n   ? mark_held_locks+0x9f/0xe0  \n   ...  \n  \nSince this bug has been confirmed to be caused by insufficient verification  \nof conn_rsp_epid, I think it would be appropriate to add a range check for  \nconn_rsp_epid to htc_connect_service() to prevent the bug from occurring. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"24 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-24T14:24:30.000000Z"}