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

Answer in brief

CVE-2026-74698 records a Unknown severity vulnerability in net/mlx5e: fix BQL reset on SQ re-activation. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 22, 2026Updated Aug 22, 2026Source checked Aug 22, 2026First seen by HOL Aug 22, 2026Material review Aug 22, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=b2588ea40ec9472688289c1a644627c0f4a1f33f <88664c48d7d1eca8e1ac92da85c89c26af741cf1 \|\| >=b2588ea40ec9472688289c1a644627c0f4a1f33f <d2897717cd222e575599d903d885c48602699800 \|\| >=b2588ea40ec9472688289c1a644627c0f4a1f33f <e7386770be1bf810bcd6af39d1e4bfeab3408430	88664c48d7d1eca8e1ac92da85c89c26af741cf1, d2897717cd222e575599d903d885c48602699800, e7386770be1bf810bcd6af39d1e4bfeab3408430
Linux/Linuxgeneric	6.17	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 88664c48d7d1eca8e1ac92da85c89c26af741cf1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 22, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.