From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72035: net/sched: sch_taprio: Replace direct dequeue call with peek and qdisc_dequeue_peeked
Date: Sat, 15 Aug 2026 15:01:54 +0900 [thread overview]
Message-ID: <2026081512-CVE-2026-72035-65da@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net/sched: sch_taprio: Replace direct dequeue call with peek and qdisc_dequeue_peeked
When taprio's software path peeks a non-work-conserving child qdisc, the
child stashes the peeked skb in its gso_skb; taprio_dequeue_from_txq()
then takes the packet with a direct child ->dequeue() call, which ignores
that stash, orphans the peeked skb and desyncs the child's qlen/backlog.
With a qfq child this re-enters the child on an emptied list and
dereferences NULL, panicking the kernel from softirq on ordinary egress.
Take the packet through qdisc_dequeue_peeked(), as sch_red and sch_sfb
now do. The helper returns the child's stashed skb first and is a no-op
when there is none, so a work-conserving child is unaffected and the
gated path now consumes the skb whose length was charged to the budget.
The Linux kernel CVE team has assigned CVE-2026-72035 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.20 with commit 5a781ccbd19e4664babcbe4b4ead7aa2b9283d22 and fixed in 6.6.145 with commit 6ee5a7665a9080bcb05d703bf981a579436fd05e
Issue introduced in 4.20 with commit 5a781ccbd19e4664babcbe4b4ead7aa2b9283d22 and fixed in 6.12.97 with commit 18d580cb00c55805633bae45e90cf22ed6b8e424
Issue introduced in 4.20 with commit 5a781ccbd19e4664babcbe4b4ead7aa2b9283d22 and fixed in 6.18.40 with commit e2b7ee61989f2d39df6c2cc06f9db1aea69bdb09
Issue introduced in 4.20 with commit 5a781ccbd19e4664babcbe4b4ead7aa2b9283d22 and fixed in 7.1.5 with commit 2dcebbd1ad2e180fe7b98bf346ced69a872e11e6
Issue introduced in 4.20 with commit 5a781ccbd19e4664babcbe4b4ead7aa2b9283d22 and fixed in 7.2-rc2 with commit e056e1dfcddca877dd46d704e8ec9860cfc9ec44
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-72035
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:
net/sched/sch_taprio.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/6ee5a7665a9080bcb05d703bf981a579436fd05e
https://git.kernel.org/stable/c/18d580cb00c55805633bae45e90cf22ed6b8e424
https://git.kernel.org/stable/c/e2b7ee61989f2d39df6c2cc06f9db1aea69bdb09
https://git.kernel.org/stable/c/2dcebbd1ad2e180fe7b98bf346ced69a872e11e6
https://git.kernel.org/stable/c/e056e1dfcddca877dd46d704e8ec9860cfc9ec44
reply other threads:[~2026-08-15 6:08 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=2026081512-CVE-2026-72035-65da@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.