net/mlx5e: fix BQL reset on SQ re-activation
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 88664c48d7d1eca8e1ac92da85c89c26af741cf1, Kernel d2897717cd222e575599d903d885c48602699800, Kernel e7386770be1bf810bcd6af39d1e4bfeab3408430 and 2 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.17, >=b2588ea40ec9472688289c1a644627c0f4a1f33f <88664c48d7d1eca8e1ac92da85c89c26af741cf1, >=b2588ea40ec9472688289c1a644627c0f4a1f33f <d2897717cd222e575599d903d885c48602699800, >=b2588ea40ec9472688289c1a644627c0f4a1f33f <e7386770be1bf810bcd6af39d1e4bfeab3408430 | 88664c48d7d1eca8e1ac92da85c89c26af741cf1, d2897717cd222e575599d903d885c48602699800, e7386770be1bf810bcd6af39d1e4bfeab3408430 |
| linux-kernel: Kernel | >=6.17.0 <6.18.45, >=6.19.0 <7.1.9 | 6.18.45, 7.1.9 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket