From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-93065: wifi: iwlwifi: fix counter type in iwl_fwrt_dump_error_logs
Date: Thu, 17 Sep 2026 17:15:44 +0100 [thread overview]
Message-ID: <2026091738-CVE-2026-93065-9db8@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
wifi: iwlwifi: fix counter type in iwl_fwrt_dump_error_logs
The loop counter 'count' was declared as u8 while num_pc is u32.
If firmware advertises more than 255 PC entries the counter wraps
back to zero and the loop never terminates potentially causing an
infinite loop or reading past the allocated pc_data array.
Change the declaration to u32 to match num_pc.
The Linux kernel CVE team has assigned CVE-2026-93065 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.5 with commit 2b69d242e29b891b11f1190201f4a08abb0c8342 and fixed in 6.6.157 with commit 8d74cb5fbb7a0d825403a74d18386dc7b22426a9
Issue introduced in 6.5 with commit 2b69d242e29b891b11f1190201f4a08abb0c8342 and fixed in 6.12.110 with commit 9710b20d09d847e07e190087b0b529673d3f1fad
Issue introduced in 6.5 with commit 2b69d242e29b891b11f1190201f4a08abb0c8342 and fixed in 6.18.52 with commit 8d8a526f3ec659194f846a2cb33844d9f6cb9995
Issue introduced in 6.5 with commit 2b69d242e29b891b11f1190201f4a08abb0c8342 and fixed in 7.2.6 with commit 769e1910d41fdd01453cef4ae032a3c162f029f8
Issue introduced in 6.5 with commit 2b69d242e29b891b11f1190201f4a08abb0c8342 and fixed in 7.3-rc1 with commit 71e67b4b59337b2f9f4fef976a27de2dad7aabf2
Issue introduced in 6.4.4 with commit ff800b0c4797c6e97f09fcd93ca8b83040d77fb4
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-93065
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/intel/iwlwifi/fw/dump.c
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/8d74cb5fbb7a0d825403a74d18386dc7b22426a9
https://git.kernel.org/stable/c/9710b20d09d847e07e190087b0b529673d3f1fad
https://git.kernel.org/stable/c/8d8a526f3ec659194f846a2cb33844d9f6cb9995
https://git.kernel.org/stable/c/769e1910d41fdd01453cef4ae032a3c162f029f8
https://git.kernel.org/stable/c/71e67b4b59337b2f9f4fef976a27de2dad7aabf2
reply other threads:[~2026-09-17 16:35 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=2026091738-CVE-2026-93065-9db8@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.