octeontx2-pf: Fix aura BPID assignment when CONFIG_DCB is enabled
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.15, 7.2.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In 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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 184fb40f731bd3353b0887731f7caba66609e9cd · fixed in 59fbbded05e559675930fd521b8d62b72828b52d; From 184fb40f731bd3353b0887731f7caba66609e9cd · fixed in 056994563935e049093f100efaad7e63ad113814; From 6.14.9 · fixed in 6.15
- Linux Linux
6.15
- KernelLinux
From 6.15.0 · fixed in 7.2.10