lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025070325-CVE-2025-38115-cce2@gregkh>
Date: Thu,  3 Jul 2025 10:35:32 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38115: net_sched: sch_sfq: fix a potential crash on gso_skb handling

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

net_sched: sch_sfq: fix a potential crash on gso_skb handling

SFQ has an assumption of always being able to queue at least one packet.

However, after the blamed commit, sch->q.len can be inflated by packets
in sch->gso_skb, and an enqueue() on an empty SFQ qdisc can be followed
by an immediate drop.

Fix sfq_drop() to properly clear q->tail in this situation.


ip netns add lb
ip link add dev to-lb type veth peer name in-lb netns lb
ethtool -K to-lb tso off                 # force qdisc to requeue gso_skb
ip netns exec lb ethtool -K in-lb gro on # enable NAPI
ip link set dev to-lb up
ip -netns lb link set dev in-lb up
ip addr add dev to-lb 192.168.20.1/24
ip -netns lb addr add dev in-lb 192.168.20.2/24
tc qdisc replace dev to-lb root sfq limit 100

ip netns exec lb netserver

netperf -H 192.168.20.2 -l 100 &
netperf -H 192.168.20.2 -l 100 &
netperf -H 192.168.20.2 -l 100 &
netperf -H 192.168.20.2 -l 100 &

The Linux kernel CVE team has assigned CVE-2025-38115 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 4.16 with commit a53851e2c3218aa30b77abd6e68cf1c371f15afe and fixed in 5.4.295 with commit c337efb20d6d9f9bbb4746f6b119917af5c886dc
	Issue introduced in 4.16 with commit a53851e2c3218aa30b77abd6e68cf1c371f15afe and fixed in 5.10.239 with commit b44f791f27b14c9eb6b907fbe51f2ba8bec32085
	Issue introduced in 4.16 with commit a53851e2c3218aa30b77abd6e68cf1c371f15afe and fixed in 5.15.186 with commit 5814a7fc3abb41f63f2d44c9d3ff9d4e62965b72
	Issue introduced in 4.16 with commit a53851e2c3218aa30b77abd6e68cf1c371f15afe and fixed in 6.1.142 with commit 9c19498bdd7cb9d854bd3c54260f71cf7408495e
	Issue introduced in 4.16 with commit a53851e2c3218aa30b77abd6e68cf1c371f15afe and fixed in 6.6.94 with commit b4e9bab6011b9559b7c157b16b91ae46d4d8c533
	Issue introduced in 4.16 with commit a53851e2c3218aa30b77abd6e68cf1c371f15afe and fixed in 6.12.34 with commit d1bc80da75c789f2f6830df89d91fb2f7a509943
	Issue introduced in 4.16 with commit a53851e2c3218aa30b77abd6e68cf1c371f15afe and fixed in 6.15.3 with commit 82448d4dcd8406dec688632a405fdcf7f170ec69
	Issue introduced in 4.16 with commit a53851e2c3218aa30b77abd6e68cf1c371f15afe and fixed in 6.16-rc2 with commit 82ffbe7776d0ac084031f114167712269bf3d832

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-2025-38115
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_sfq.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/c337efb20d6d9f9bbb4746f6b119917af5c886dc
	https://git.kernel.org/stable/c/b44f791f27b14c9eb6b907fbe51f2ba8bec32085
	https://git.kernel.org/stable/c/5814a7fc3abb41f63f2d44c9d3ff9d4e62965b72
	https://git.kernel.org/stable/c/9c19498bdd7cb9d854bd3c54260f71cf7408495e
	https://git.kernel.org/stable/c/b4e9bab6011b9559b7c157b16b91ae46d4d8c533
	https://git.kernel.org/stable/c/d1bc80da75c789f2f6830df89d91fb2f7a509943
	https://git.kernel.org/stable/c/82448d4dcd8406dec688632a405fdcf7f170ec69
	https://git.kernel.org/stable/c/82ffbe7776d0ac084031f114167712269bf3d832

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ