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

net/mlx5e: fix BQL reset on SQ re-activation

mlx5e_queue_start() deactivates and re-activates all channels but closes
only the queue being restarted. mlx5e_activate_txqsq() then
unconditionally calls netdev_tx_reset_queue(), zeroing the BQL counters
of channels that kept their in-flight TX WQEs. The next completion then
over-charges and trips the BUG_ON() in dql_completed():

kernel BUG at lib/dynamic_queue_limits.c:99!
RIP: 0010:dql_completed+0x23d/0x280
Call Trace:
<IRQ>
mlx5e_poll_tx_cq+0x668/0xa60
mlx5e_napi_poll+0x5b/0x7b0
net_rx_action+0x15a/0x580

Reset BQL only when the SQ has no bytes in flight (sq->cc == sq->pc).

In the case that reset is skipped, the outstanding WQEs will eventually
complete and rebalance the dql. The dql->limit is carried across the
reset.
Published: 2026-08-22
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Kernel Crash / Denial of Service
Action: Update Kernel
AI Analysis

Impact

The defect resides in the Linux kernel network driver for Mellanox mlx5e. When a send queue is deactivated and re‑activated, the driver calls a routine that unconditionally resets the BQL (Dynamic Queue Limits) counters for all channels even if there are in‑flight transmit work queue elements. The reset over‑stores the BQL limits, and a subsequent completion that over‑charges the queue triggers an internal BUG_ON. This causes the kernel to panic, resulting in an immediate denial of service. The weakness originates from improper initialization of queue state and violates the kernel’s invariant that BQL counters must only be cleared when no data is outstanding.

Affected Systems

Based on the commit references, it is inferred that all Linux kernel installations that contain the mlx5e network driver are affected. The vendor is Linux, the product is the Linux kernel. The specific kernel releases are not listed, but the commit references point to a change in the mainline tree that will apply to all supported kernels after the patch is merged.

Risk and Exploitability

The CVSS score is 5.5, and the EPSS score is < 1%, indicating a very low exploitation probability. The quantitative likelihood of exploitation can be considered low based on the EPSS value. Based on the description, it is inferred that a BUG_ON will be triggered on a completed transmission after a faulty reset; the bug is triggered by normal network traffic handling, so it can be exercised by any local user who can cause a queue re‑activation. The vulnerability is not listed in CISA KEV catalog, indicating no documented active exploitation. The risk remains significant because a kernel panic completely disrupts the system, but the exploitation vector requires local access to trigger the driver’s re‑activation path.

Generated by OpenCVE AI on August 25, 2026 at 14:42 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the kernel patch that includes the commit 88664c48d7d1eca8e1ac92da85c89c26af741cf1 (or its equivalent merge that resets BQL only when the queue has no bytes in flight).
  • Reboot the system so that the updated kernel image is active.
  • If the patch is not available for your current kernel version, upgrade to a kernel version that contains the commit or wait for an official release.

Generated by OpenCVE AI on August 25, 2026 at 14:42 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 25 Aug 2026 12:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-617
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Low


Sat, 22 Aug 2026 15:45:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: fix BQL reset on SQ re-activation mlx5e_queue_start() deactivates and re-activates all channels but closes only the queue being restarted. mlx5e_activate_txqsq() then unconditionally calls netdev_tx_reset_queue(), zeroing the BQL counters of channels that kept their in-flight TX WQEs. The next completion then over-charges and trips the BUG_ON() in dql_completed(): kernel BUG at lib/dynamic_queue_limits.c:99! RIP: 0010:dql_completed+0x23d/0x280 Call Trace: <IRQ> mlx5e_poll_tx_cq+0x668/0xa60 mlx5e_napi_poll+0x5b/0x7b0 net_rx_action+0x15a/0x580 Reset BQL only when the SQ has no bytes in flight (sq->cc == sq->pc). In the case that reset is skipped, the outstanding WQEs will eventually complete and rebalance the dql. The dql->limit is carried across the reset.
Title net/mlx5e: fix BQL reset on SQ re-activation
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-22T15:32:59.703Z

Reserved: 2026-08-15T05:44:03.927Z

Link: CVE-2026-74698

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-22T16:16:44.397

Modified: 2026-08-22T16:16:44.397

Link: CVE-2026-74698

cve-icon Redhat

Severity : Low

Publid Date: 2026-08-22T00:00:00Z

Links: CVE-2026-74698 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-25T14:45:03Z

Weaknesses