From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-68349: wifi: carl9170: fix buffer overflow in rx_stream failover path
Date: Mon, 10 Aug 2026 14:01:06 +0200 [thread overview]
Message-ID: <2026081038-CVE-2026-68349-aa62@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
wifi: carl9170: fix buffer overflow in rx_stream failover path
The failover continuation in carl9170_rx_stream() copies the full tlen
from the second USB transfer instead of capping at rx_failover_missing
bytes. When both transfers are near maximum size, the total exceeds the
65535-byte failover SKB, triggering skb_over_panic.
Limit the copy size to the missing byte count.
[Fix checkpatch CHECK:PARENTHESIS_ALIGNMENT]
The Linux kernel CVE team has assigned CVE-2026-68349 to this issue.
Affected and fixed versions
===========================
Issue introduced in 2.6.37 with commit a84fab3cbfdc427e7d366f1cc844f27b2084c26c and fixed in 6.6.148 with commit 5acfa18de66b6089b81c1c0bf1a3ae3c940ec39e
Issue introduced in 2.6.37 with commit a84fab3cbfdc427e7d366f1cc844f27b2084c26c and fixed in 6.12.101 with commit b9dfee5e63ee9b5c47be9e344ebc5bd3f43fca78
Issue introduced in 2.6.37 with commit a84fab3cbfdc427e7d366f1cc844f27b2084c26c and fixed in 6.18.42 with commit 4503829843353dbb18b879c35be1cdfc9af677b7
Issue introduced in 2.6.37 with commit a84fab3cbfdc427e7d366f1cc844f27b2084c26c and fixed in 7.1.6 with commit 21f59906ea75618fdd46a7e32754d54fbee083ea
Issue introduced in 2.6.37 with commit a84fab3cbfdc427e7d366f1cc844f27b2084c26c and fixed in 7.2-rc5 with commit a1a21995c2e1cc2ca6b2226cfe4f5f018370182a
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-68349
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/carl9170/rx.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/5acfa18de66b6089b81c1c0bf1a3ae3c940ec39e
https://git.kernel.org/stable/c/b9dfee5e63ee9b5c47be9e344ebc5bd3f43fca78
https://git.kernel.org/stable/c/4503829843353dbb18b879c35be1cdfc9af677b7
https://git.kernel.org/stable/c/21f59906ea75618fdd46a7e32754d54fbee083ea
https://git.kernel.org/stable/c/a1a21995c2e1cc2ca6b2226cfe4f5f018370182a
reply other threads:[~2026-08-10 12:11 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=2026081038-CVE-2026-68349-aa62@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.