Live › vulnerability › CVE-2026-98806
Go to dashboardIn the Linux kernel's octeontx2 network driver, buffer pool ID assignment dereferenced an uninitialized PFC map when DCB was enabled, which affected SDP virtual functions. The fix adds a NULL check and assigns a default ID first, so the driver no longer reads invalid memory.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running a Linux kernel built with CONFIG_DCB enabled that use Marvell octeontx2 (OcteonTX2) network hardware with SDP virtual functions. Standard x86 or general-purpose servers without this hardware are unlikely to be affected. The sources do not give fixed kernel versions.
No product ranges from the sources yet.
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-98806")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.