[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025061827-CVE-2025-38039-919c@gregkh>
Date: Wed, 18 Jun 2025 11:33:35 +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-38039: net/mlx5e: Avoid WARN_ON when configuring MQPRIO with HTB offload enabled
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net/mlx5e: Avoid WARN_ON when configuring MQPRIO with HTB offload enabled
When attempting to enable MQPRIO while HTB offload is already
configured, the driver currently returns `-EINVAL` and triggers a
`WARN_ON`, leading to an unnecessary call trace.
Update the code to handle this case more gracefully by returning
`-EOPNOTSUPP` instead, while also providing a helpful user message.
The Linux kernel CVE team has assigned CVE-2025-38039 to this issue.
Affected and fixed versions
===========================
Fixed in 6.6.93 with commit 090c0ba179eaf7b670e720aa054533756a43d565
Fixed in 6.12.31 with commit b82e496531c571caf8a2ef247f51c160bab2162e
Fixed in 6.14.9 with commit 9e2bac6835f73895598df5a3a125a19497fad46b
Fixed in 6.15 with commit 689805dcc474c2accb5cffbbcea1c06ee4a54570
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-38039
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/mellanox/mlx5/core/en_main.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/090c0ba179eaf7b670e720aa054533756a43d565
https://git.kernel.org/stable/c/b82e496531c571caf8a2ef247f51c160bab2162e
https://git.kernel.org/stable/c/9e2bac6835f73895598df5a3a125a19497fad46b
https://git.kernel.org/stable/c/689805dcc474c2accb5cffbbcea1c06ee4a54570
Powered by blists - more mailing lists