CVE-2024-53156

wifi: ath9k: add range check for conn_rsp_epid in htc_connect_service()

Description

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.

Category

7.8
CVSS
Severity: High
CVSS 3.1 •
EPSS 0.02%
Affected: Linux Linux
Affected: Linux Linux
Published at:
Updated at:

References

Link Tags
https://git.kernel.org/stable/c/5f177fb9d01355ac183e65ad8909ea8ef734e0cf patch
https://git.kernel.org/stable/c/cb480ae80fd4d0f1ac9e107ce799183beee5124b patch
https://git.kernel.org/stable/c/c941af142200d975dd3be632aeb490f4cb91dae4 patch
https://git.kernel.org/stable/c/8965db7fe2e913ee0802b05fc94c6d6aa74e0596 patch
https://git.kernel.org/stable/c/70eae50d2156cb6e078d0d78809b49bf2f4c7540 patch
https://git.kernel.org/stable/c/b6551479daf2bfa80bfd5d9016b02a810e508bfb patch
https://git.kernel.org/stable/c/3fe99b9690b99606d3743c9961ebee865cfa1ab8 patch
https://git.kernel.org/stable/c/bc981179ab5d1a2715f35e3db4e4bb822bacc849 patch
https://git.kernel.org/stable/c/8619593634cbdf5abf43f5714df49b04e4ef09ab patch

Frequently Asked Questions

What is the severity of CVE-2024-53156?
CVE-2024-53156 has been scored as a high severity vulnerability.
How to fix CVE-2024-53156?
To fix CVE-2024-53156, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2024-53156 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2024-53156 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2024-53156?
CVE-2024-53156 affects Linux Linux, Linux Linux.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.