[CVE-2026-98806][MODERATE REGULAR] octeontx2-pf: Fix aura BPID assignment when CONFIG_DCB is enabled [ Upstream

[CVE-2026-98806][MODERATE REGULAR] octeontx2-pf: Fix aura BPID assignment when CONFIG_DCB is enabled [ Upstream

[AL-KERNEL]

CVE: CVE-2026-98806
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: octeontx2-pf: Fix aura BPID assignment when CONFIG_DCB is enabled [ Upstream
Commit: 59fbbded05e559675930fd521b8d62b72828b52d
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=59fbbded05e559675930fd521b8d62b72828b52d
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98806
Analysis date: Sun, 18 Oct 2026 22:20:18 -0400
ActionableScore: 1
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
A missing NULL check in octeontx2 BPID selection can dereference an uninitialized queue_to_pfc_map for SDP VFs with CONFIG_DCB, causing device initialization failure or a possible kernel Oops, while guest or delegated triggerability remains unproven.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-98806 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98806

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: MODERATE REGULAR
Manual review required: NO

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-98806	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-98806 CHECK WITH IMPACT FROM ORIG NN IMPORTANT | AEGIS IMPACT MODERATE_KPANIC AEGIS_AS=0 LEGACY=MODERATE RESULT=DIFF (final Legacy and Aegis differ; FINAL: MODERATE, Aegis: MODERATE_KPANIC)	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H';**CWE-476;CWE-754;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.5';DESCR 'A NULL pointer dereference can occur in the Marvell octeontx2 driver because BPID selection reads queue_to_pfc_map when CONFIG_DCB is enabled even though this map is not initialized for SDP VFs. The invalid access is reached while CQ or aura resources are initialized and can cause a kernel Oops, prevent the network device from starting, or crash the host when panic on Oops is enabled. The issue is not directly network reachable because ordinary packet traffic does not provide the demonstrated trigger. For the CVSS the PR:L value in the paranoid score represents an environment where a reduced capability service, container administrator, or delegated VF user can cause VF initialization or recovery without full host administrator rights. The confirmed primitive is a NULL pointer read rather than UAF, OOB write, or arbitrary write. Impact is therefore denial of service, with no supported confidentiality or integrity impact. Automated impact decision path. The original SimpleNet classifier selected IMPORTANT. The primary LLM estimated paranoid CVSS 5.5 and the production ActionableScore returned 1 with recommendation Ordinary Moderate. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. Recorded rule transitions were CVSS and initial triage stage IMPORTANT to MODERATE_KPANIC because the CVSS score, vector or bug class threshold rule was applied. ActionableScore thresholds stage MODERATE_KPANIC to MODERATE because the ActionableScore threshold rule was applied. The legacy KP specialist has no review artifact for this run. The legacy FD or DH downgrade specialist has no review artifact for this run. Exact triggered rule markers were LOWERED_FROM_HIGH_BASED_ON_GUESSCVSS and DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN4 and V41_INHERITED_KPANIC_PROMOTION_BLOCKED. The independent weaker Aegis shadow evaluated CVSS 2.3 and ActionableScore 0 with primitive class CLASS_C and manual review NO. Its independently reconciled impact was MODERATE_KPANIC. The models disagreed but the aggregation rules retained the production result. The final reported impact is MODERATE.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1)	MAYBE	REMOTE SIMPLEFIX NETWORK LINUS  LOWERED_FROM_HIGH_BASED_ON_GUESSCVSS  DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN4 V41_INHERITED_KPANIC_PROMOTION_BLOCKED	-	-	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=1
ActionableScoreLower=0
PrimitiveClass=CLASS_C
RealUAF=NO
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=UNKNOWN
ImportantCandidate=NO
ManualReview=RECOMMENDED
AutoDowngradeAllowed=YES
RequiresHostUID0=UNKNOWN
AuthorizationDecisionBypass=NO
ProtectedResourceImpact=NONE
B4PendingReview=NO
B4PendingConfirmed=NO

## 1. ActionableScore

* Raw conservative score: 0
* Conservative score: 0
* Raw paranoid score: 1
* Paranoid score: 1
* No floor or cap was applied.
* Final recommended bucket: **Ordinary Moderate**::

The paranoid score adds one point for a plausible kernel Oops or host crash from the NULL access. The conservative score does not treat host-wide failure as established because the supplied evidence only confirms invalid memory access during device resource initialization.

## 2. Signal breakdown

### Conservative

* +0 Weak invalid-pointer concern. `queue_to_pfc_map` is dereferenced while NULL, but this is an invalid read rather than an OOB write, UAF, or active-object corruption.
* +0 No confirmed host-wide crash. Device initialization failure or loss of the affected network interface is supported more directly than a kernel panic.
* +0 No privilege penalty. The complete trigger privilege is unresolved, so host-admin privilege is not assumed.
* +0 No hardware penalty. Specific Marvell hardware and an SDP VF are required, but rarity and physical-only attacker access are not established.

Raw conservative score: 0.

### Paranoid

* +1 Reliable kernel crash or strong DoS concern. A kernel NULL dereference can produce an Oops and may panic the host under fatal-Oops policy or a critical execution context.

Raw paranoid score: 1.

### Material signals not awarded

* No UAF, stale lifetime, double release, or refcount mutation is present.
* No heap or slab OOB write is established. B5-R does not apply.
* No attacker-influenced active structured-state write is established. V33 does not apply.
* No checksum metadata or downstream packet-header corruption exists. V32 and V34 do not apply.
* No shared-backing or file-backed write exists. B3-PENDING does not apply.
* No authorization decision changes from DENY to ALLOW. B4-PENDING does not apply.
* No arbitrary write, controlled reclaim, disclosure, privilege escalation, or integrity primitive is demonstrated.
* Firmware-mediated attacker influence is not awarded because the patch does not show that a VF guest or remote peer controls the failing initialization sequence.
* No extra Availability point is awarded because device failure and a possible Oops are variants of the same immediate fault.

## 3. Reachability analysis

The vulnerable reads occur in `cn20k_aura_aq_init()`, `otx2_cq_init()`, and `otx2_aura_aq_init()` while configuring CQ or aura backpressure. The required state includes `CONFIG_DCB`, an SDP VF, and an uninitialized `queue_to_pfc_map`.

The supplied code does not establish whether an untrusted VF guest, delegated device-management service, container, or ordinary local user can cause the complete initialization or recovery sequence. Ordinary network packets do not directly control `queue_to_pfc_map` or reach this dereference.

Provisioning or resetting an SDP VF may involve host-side device management, but the evidence does not prove that host-admin-equivalent privilege is required for every complete trigger. Therefore:

* Host-admin requirement: unknown.
* Namespace-scoped trigger: unknown.
* Remote packet trigger: not established.
* Prior physical or virtual device setup: required.
* Race or timing requirement: none shown. The fault appears deterministic once the affected configuration reaches these initialization paths.

## 4. Primitive and severity interpretation

The exact primitive is an invalid read through a NULL `queue_to_pfc_map` pointer. The resulting value is intended to select an entry from `pfvf->bpid`, but on normal kernels the initial NULL-based read should fault before useful attacker-controlled state is obtained or consumed.

This is neither fixed stale storage nor an active structured-object UAF. There is no first lifetime-ending operation, surviving dangling reference, or second lifetime mutation.

The issue is classified as CLASS_C because the demonstrated behavior is invalid access during device initialization, with device failure or kernel Oops as the plausible consequence. A host panic is possible but not confirmed as reliable. There is no independent non-crash corruption primitive.

ImportantCandidate is NO because no active-state write, security-boundary bypass, shared-backing modification, or memory-corruption primitive is established. AutoDowngradeAllowed is YES because the unresolved question concerns the scope of availability impact and trigger privilege, not an unresolved Important-grade corruption primitive.

## 5. One-sentence report phrase

A missing NULL check in octeontx2 BPID selection can dereference an uninitialized queue_to_pfc_map for SDP VFs with CONFIG_DCB, causing device initialization failure or a possible kernel Oops, while guest or delegated triggerability remains unproven.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Verify whether an untrusted SDP VF or delegated virtualization service can independently initiate the affected CQ or aura initialization or recovery path and whether the observed fault is device-local or host-fatal.

## 7. Call-site confidence

Call-site confidence: high

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: octeontx2-pf: Fix aura BPID assignment when CONFIG_DCB is enabled [ Upstream
Commit: 59fbbded05e559675930fd521b8d62b72828b52d
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=59fbbded05e559675930fd521b8d62b72828b52d

Changed files:
  drivers/net/ethernet/marvell/octeontx2/nic/cn20k.c
  drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.c
  drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.h

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=59fbbded05e559675930fd521b8d62b72828b52d

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-98806 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98806

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L
  The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 5.5

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 0
  Paranoid ActionableScore: 1

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: MODERATE
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): MODERATE REGULAR

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).