CVE-2024-53156

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

HIGH

7.8

CVSS Score

Published: December 24, 2024 at 11:28 AM UTC

Updated: June 17, 2026 at 08:08 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.8

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

2.6.35 ≤ v < 4.19.3252.6.35 ≤ v < 5.10.2312.6.35 ≤ v < 5.15.1742.6.35 ≤ v < 5.4.2872.6.35 ≤ v < 6.1.1202.6.35 ≤ v < 6.11.112.6.35 ≤ v < 6.12.22.6.35 ≤ v < 6.132.6.35 ≤ v < 6.6.644.20 ≤ v < 5.4.2875.11 ≤ v < 5.15.1745.16 ≤ v < 6.1.1205.5 ≤ v < 5.10.2316.12 ≤ v < 6.12.26.2 ≤ v < 6.6.646.7 ≤ v < 6.11.112.6.35fb9987d0f748c983bb795a86f47522313f701a08

Vendor states this is fixed in 3fe99b9690b99606d3743c9961ebee865cfa1ab8 (fixed)

Vendor states this is fixed in 5f177fb9d01355ac183e65ad8909ea8ef734e0cf (fixed)

Vendor states this is fixed in 70eae50d2156cb6e078d0d78809b49bf2f4c7540 (fixed)

Vendor states this is fixed in 8619593634cbdf5abf43f5714df49b04e4ef09ab (fixed)

Vendor states this is fixed in 8965db7fe2e913ee0802b05fc94c6d6aa74e0596 (fixed)

Vendor states this is fixed in b6551479daf2bfa80bfd5d9016b02a810e508bfb (fixed)

Vendor states this is fixed in bc981179ab5d1a2715f35e3db4e4bb822bacc849 (fixed)

Vendor states this is fixed in c941af142200d975dd3be632aeb490f4cb91dae4 (fixed)

Vendor states this is fixed in cb480ae80fd4d0f1ac9e107ce799183beee5124b (fixed)

Vendor states this is fixed in 2.6.35 (unaffected)

Vendor states this is fixed in 4.19.325 (unaffected)

Vendor states this is fixed in 5.10.231 (unaffected)

Vendor states this is fixed in 5.15.174 (unaffected)

Vendor states this is fixed in 5.4.287 (unaffected)

Vendor states this is fixed in 6.1.120 (unaffected)

Vendor states this is fixed in 6.11.11 (unaffected)

Vendor states this is fixed in 6.12.2 (unaffected)

Vendor states this is fixed in 6.13 (unaffected)

Vendor states this is fixed in 6.6.64 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references