octeontx2-pf: Fix aura BPID assignment when CONFIG_DCB is enabled
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 |
|
|
7.2.107.3In the Linux kernel, the following vulnerability has been resolved:
octeontx2-pf: Fix aura BPID assignment when CONFIG_DCB is enabled
Previously, BPID assignment under CONFIG_DCB assumed `queue_to_pfc_map` was always initialized. For SDP VFs this leads to invalid memory access as it was not initialized.
This patch adds a NULL check for `queue_to_pfc_map` before dereferencing it. Also, simplifies the logic by always assigning a default BPID first, then conditionally overriding it if CONFIG_DCB is enabled and the map exists.
From the CVE record · Linux
The octeontx2-pf driver can access invalid memory when CONFIG_DCB is enabled for SDP VFs because it assumes queue_to_pfc_map is initialized. The input does not specify whether an attacker can trigger this or what access or interaction would be required.
Engineers running the Linux kernel with the octeontx2-pf driver and CONFIG_DCB enabled should check their installations; affected versions are not specified.