linux-cve-announce - CVE-2025-38278: octeontx2-pf: QOS: Refactor TC_HTB_LEAF_DEL

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: <2025071009-CVE-2025-38278-2d3a@gregkh>
Date: Thu, 10 Jul 2025 09:42:19 +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-38278: octeontx2-pf: QOS: Refactor TC_HTB_LEAF_DEL_LAST callback

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

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

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

octeontx2-pf: QOS: Refactor TC_HTB_LEAF_DEL_LAST callback

This patch addresses below issues,

1. Active traffic on the leaf node must be stopped before its send queue
   is reassigned to the parent. This patch resolves the issue by marking
   the node as 'Inner'.

2. During a system reboot, the interface receives TC_HTB_LEAF_DEL
   and TC_HTB_LEAF_DEL_LAST callbacks to delete its HTB queues.
   In the case of TC_HTB_LEAF_DEL_LAST, although the same send queue
   is reassigned to the parent, the current logic still attempts to update
   the real number of queues, leadning to below warnings

        New queues can't be registered after device unregistration.
        WARNING: CPU: 0 PID: 6475 at net/core/net-sysfs.c:1714
        netdev_queue_update_kobjects+0x1e4/0x200

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


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

	Issue introduced in 6.5 with commit 5e6808b4c68d7882971514ab3279926eb07c8b2d and fixed in 6.6.94 with commit 5df8db01d6a4e9c35a5ba5d7e130d5cecd3ffcb4
	Issue introduced in 6.5 with commit 5e6808b4c68d7882971514ab3279926eb07c8b2d and fixed in 6.12.34 with commit ec62c99914a79d84c8de5ba1b94d62f2ed721f2a
	Issue introduced in 6.5 with commit 5e6808b4c68d7882971514ab3279926eb07c8b2d and fixed in 6.15.3 with commit f1fca0eae5a0573f226f46c6871260278e7dda12
	Issue introduced in 6.5 with commit 5e6808b4c68d7882971514ab3279926eb07c8b2d and fixed in 6.16-rc1 with commit 67af4ec948e8ce3ea53a9cf614d01fddf172e56d

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-38278
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/ethernet/marvell/octeontx2/nic/qos.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/5df8db01d6a4e9c35a5ba5d7e130d5cecd3ffcb4
	https://git.kernel.org/stable/c/ec62c99914a79d84c8de5ba1b94d62f2ed721f2a
	https://git.kernel.org/stable/c/f1fca0eae5a0573f226f46c6871260278e7dda12
	https://git.kernel.org/stable/c/67af4ec948e8ce3ea53a9cf614d01fddf172e56d