Bug 2555242 (CVE-2026-98806)

Summary: CVE-2026-98806 kernel: octeontx2-pf: Fix aura BPID assignment when CONFIG_DCB is enabled
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: akhatavk, aos-team-art-private, asdas, dpaolell, jdelft, jupierce, lgarciaa, mbiarnes, ppalepu, ppostler, prdhamdh, rhel-process-autobot, sghai, sidsharm, suppawar, vlaad, watson-tool-maintainers
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in the Linux kernel's octeontx2-pf network driver. When Data Center Bridging (DCB) is enabled, the driver assumes traffic queue mapping structures are always initialized, which is not the case for System Data Path (SDP) virtual functions. This issue leads to a NULL pointer dereference during backpressure identifier assignment, allowing a local user to crash the system and cause a Denial of Service (DoS) via an invalid memory access.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-10-18 16:04:10 UTC
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.