From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-97541: wifi: ath9k_htc: don't store usb_device_id
Date: Fri, 25 Sep 2026 12:22:01 +0200 [thread overview]
Message-ID: <2026092549-CVE-2026-97541-ebe8@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
wifi: ath9k_htc: don't store usb_device_id
usb_device_id is not guaranteed to live longer than probe due to presence
of dynamic ID. All information apart from driver_data can be easily
retrieved from usb_device, so just store driver_data.
The Linux kernel CVE team has assigned CVE-2026-97541 to this issue.
Affected and fixed versions
===========================
Fixed in 6.12.111 with commit 8e70a6785bd02cf9ef7fd21ebccf46a8ba23014e
Fixed in 6.18.53 with commit 9d5e396578097d02e859798207db41ed4b831f50
Fixed in 7.2.7 with commit c34aa59950597e3360e9cef9d08cdf4edb30ad4d
Fixed in 7.3-rc1 with commit 14d2ac442d660e112efc0ce87ad10085013ed2b1
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-97541
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/net/wireless/ath/ath9k/hif_usb.c
drivers/net/wireless/ath/ath9k/hif_usb.h
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/8e70a6785bd02cf9ef7fd21ebccf46a8ba23014e
https://git.kernel.org/stable/c/9d5e396578097d02e859798207db41ed4b831f50
https://git.kernel.org/stable/c/c34aa59950597e3360e9cef9d08cdf4edb30ad4d
https://git.kernel.org/stable/c/14d2ac442d660e112efc0ce87ad10085013ed2b1
reply other threads:[~2026-09-25 10:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026092549-CVE-2026-97541-ebe8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.