CVE-2024-53156

HIGH EPSS 14.0%
Published Dec 24, 20241y ago · Modified Jun 17, 20261w ago
7.8 CVSS 3.1
High
Find Similar
Published Dec 24, 2024 1y ago
Last Modified Jun 17, 2026 1w ago

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.

CVSS Details

Base Score
7.8
Exploitability
1.8
Impact
5.9
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Attack Vector Local
Attack Complexity Low
Privileges Required Low
User Interaction None
Scope Unchanged
Confidentiality High
Integrity High
Availability High

Threat Intelligence

EPSS Exploit Probability
14.0% percentile
Exploit & Patch Status
No Known Exploit
Patch Available

Weaknesses 1

CWE-129

Affected Products 8

VendorProductVersionRange
linuxlinux_kernel*≥2.6.35  –  <4.19.325
linuxlinux_kernel*≥4.20  –  <5.4.287
linuxlinux_kernel*≥5.5  –  <5.10.231
linuxlinux_kernel*≥5.11  –  <5.15.174
linuxlinux_kernel*≥5.16  –  <6.1.120
linuxlinux_kernel*≥6.2  –  <6.6.64
linuxlinux_kernel*≥6.7  –  <6.11.11
linuxlinux_kernel*≥6.12  –  <6.12.2

References 11

  • git.kernel.org https://git.kernel.org/stable/c/3fe99b9690b99606d3743c9961ebee865cfa1ab8
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/5f177fb9d01355ac183e65ad8909ea8ef734e0cf
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/70eae50d2156cb6e078d0d78809b49bf2f4c7540
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/8619593634cbdf5abf43f5714df49b04e4ef09ab
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/8965db7fe2e913ee0802b05fc94c6d6aa74e0596
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/b6551479daf2bfa80bfd5d9016b02a810e508bfb
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/bc981179ab5d1a2715f35e3db4e4bb822bacc849
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/c941af142200d975dd3be632aeb490f4cb91dae4
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/cb480ae80fd4d0f1ac9e107ce799183beee5124b
    Patch
  • lists.debian.org https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html
  • lists.debian.org https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html

Remediation

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