CVE-2026-74698
Description
A flaw was found in the Linux kernel's net/mlx5e driver. When a Send Queue (SQ) is re-activated, the Byte Queue Limits (BQL) counters are incorrectly reset even if there are still network transmissions in progress. This can lead to an inconsistent state, causing the kernel to trigger an error and resulting in a system crash, effectively a denial of service.
Statement
A flaw of low impact was found in the Linux kernel's net/mlx5e driver, affecting the kernel in Red Hat Enterprise Linux 9.8, 9.9, 10.2 and 10.3 and in Red Hat In-Vehicle OS 2.0 and 2.1. When a Send Queue (SQ) is re-activated via the mlx5e queue management operations, mlx5e_activate_txqsq() unconditionally calls netdev_tx_reset_queue(), zeroing the Byte Queue Limits (BQL) counters of channels that still have transmit work queue entries (WQEs) in flight. The next TX completion then over-charges the dynamic queue limits (dql) accounting and trips the BUG_ON() in dql_completed(), causing a kernel panic in IRQ/NAPI context and crashing the system, i.e. a denial of service limited to availability. Triggering the vulnerable transition requires privileged local access to reconfigure or re-activate network queues while transmit traffic is still outstanding; it is not directly reachable through remote network traffic alone, which is why Red Hat Product Security rates this flaw as Low impact despite the Red Hat CVSS:3.1 base score of 5.5 (MODERATE, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). The vulnerable code was introduced together with the mlx5e queue management operations and single channel swap support, so earlier Red Hat Enterprise Linux streams (RHEL 7, 8, 9.2, 9.4, 9.6 and 10.0) are not affected because the vulnerable code is not present. For the affected streams the fix is currently deferred; the residual risk is that a privileged local action that restarts a network queue while transmissions are in flight can panic the kernel.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Crash, Exit, or Restart
While assertion is good for catching logic errors and reducing the chances of reaching more serious vulnerability conditions, an attacker can still cause a denial of service if they can trigger an assert statement, and if the scope of the assert() extends beyond the attacker's own session. For example, if a server handles multiple simultaneous connections, if an assert() occurs in one single connection that causes all other connections to be dropped, this could be a significant denial of service.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.