net: bnxt: ring the doorbell when SW USO exits early
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: bnxt: ring the doorbell when SW USO exits early
When a burst of packets is handed down to the driver, the driver defers the doorbell to the end by setting txr->kick_pending = 1. The normal TX path handles this, but the SW USO path can miss it if it returns early.
If bnxt_sw_udp_gso_xmit runs but returns early with NETDEV_TX_BUSY and txr->kick_pending was previously set to 1, then the TX queue can stall because the driver wrote some BDs but never wrote the doorbell. The device won't know to do the TX which would generate the completion that would wake the queue back up.
Simplify bnxt_sw_udp_gso_xmit to set txr->kick_pending in its success case and check the flag on return. The added check after bnxt_sw_udp_gso_xmit returns ensures that any pending doorbells are written handling both successful USO and any early returns, which prevents the TX queue stall mentioned above.
This TX queue stall was observed on a production system with a netdev TX watchdog informing about the queue stall.
From the CVE record · Linux
The Linux kernel's bnxt driver can stall a transmit queue if software UDP segmentation offload returns early with NETDEV_TX_BUSY while a doorbell is pending. The device may then miss the notification needed to complete transmission and wake the queue. The input does not establish an attacker-controlled trigger or specify authentication or user-interaction requirements.
Administrators running Linux systems that use the bnxt network driver should check their kernel versions; affected versions were not provided.