wifi: ath9k: add range check for conn_rsp_epid in htc_connect_service()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 3fe99b9690b99606d3743c9961ebee865cfa1ab8, Kernel 5f177fb9d01355ac183e65ad8909ea8ef734e0cf, Kernel 70eae50d2156cb6e078d0d78809b49bf2f4c7540 and 6 more.
In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: add range check for conn_rsp_epid in htc_connect_service() I found the following bug in my fuzzer: UBSAN: array-index-out-of-bounds in drivers/net/wireless/ath/ath9k/htc_hst.c:26:51 index 255 is out of range for type 'htc_endpoint [22]' CPU: 0 UID: 0 PID: 8 Comm: kworker/0:0 Not tainted 6.11.0-rc6-dirty #14 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Workqueue: events request_firmware_work_func Call Trace: <TASK> dump_stack_lvl+0x180/0x1b0 __ubsan_handle_out_of_bounds+0xd4/0x130 htc_issue_send.constprop.0+0x20c/0x230 ? _raw_spin_unlock_irqrestore+0x3c/0x70 ath9k_wmi_cmd+0x41d/0x610 ? mark_held_locks+0x9f/0xe0 ... Since this bug has been confirmed to be caused by insufficient verification of conn_rsp_epid, I think it would be appropriate to add a range check for conn_rsp_epid to htc_connect_service() to prevent the bug from occurring.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =2.6.35, >=fb9987d0f748c983bb795a86f47522313f701a08 <3fe99b9690b99606d3743c9961ebee865cfa1ab8, >=fb9987d0f748c983bb795a86f47522313f701a08 <5f177fb9d01355ac183e65ad8909ea8ef734e0cf, >=fb9987d0f748c983bb795a86f47522313f701a08 <70eae50d2156cb6e078d0d78809b49bf2f4c7540, >=fb9987d0f748c983bb795a86f47522313f701a08 <8619593634cbdf5abf43f5714df49b04e4ef09ab, >=fb9987d0f748c983bb795a86f47522313f701a08 <8965db7fe2e913ee0802b05fc94c6d6aa74e0596, >=fb9987d0f748c983bb795a86f47522313f701a08 <b6551479daf2bfa80bfd5d9016b02a810e508bfb, >=fb9987d0f748c983bb795a86f47522313f701a08 <bc981179ab5d1a2715f35e3db4e4bb822bacc849, >=fb9987d0f748c983bb795a86f47522313f701a08 <c941af142200d975dd3be632aeb490f4cb91dae4, >=fb9987d0f748c983bb795a86f47522313f701a08 <cb480ae80fd4d0f1ac9e107ce799183beee5124b | 3fe99b9690b99606d3743c9961ebee865cfa1ab8, 5f177fb9d01355ac183e65ad8909ea8ef734e0cf, 70eae50d2156cb6e078d0d78809b49bf2f4c7540, 8619593634cbdf5abf43f5714df49b04e4ef09ab, 8965db7fe2e913ee0802b05fc94c6d6aa74e0596, b6551479daf2bfa80bfd5d9016b02a810e508bfb, bc981179ab5d1a2715f35e3db4e4bb822bacc849, c941af142200d975dd3be632aeb490f4cb91dae4, cb480ae80fd4d0f1ac9e107ce799183beee5124b |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket