eth: fbnic: Handle maximum standalone channels
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:
eth: fbnic: Handle maximum standalone channels
Standalone channels use one NAPI vector for each Tx and Rx queue. fbnic's allocation path excludes FBNIC_MAX_TXQS from that layout. A 64-Tx/64-Rx configuration therefore records 128 vectors but allocates only 64, leaving NULL entries that resource setup dereferences.
Include the maximum vector count in standalone allocation.
From the CVE record · Linux
The fbnic driver allocates too few vectors for a standalone configuration with 64 Tx and 64 Rx queues. Resource setup then dereferences NULL entries; the input does not specify how an attacker could reach this configuration or whether authentication or user interaction is required.
Engineers running Linux kernels with the fbnic driver should check their installations; affected versions are not specified.