[CVE-2026-68375][LOW] bnxt_en: Handle partially initialized auxiliary devices [ Upstream

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-68375
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: bnxt_en: Handle partially initialized auxiliary devices [ Upstream
Commit: 4e1caa5fdd0dea36938fe39cceb1522e9d86c937
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4e1caa5fdd0dea36938fe39cceb1522e9d86c937
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68375
Analysis date: Mon, 10 Aug 2026 11:17:14 -0400
ActionableScore: 2
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like, auto-close candidate
Manual review required: NO

Summary:
bnxt_en auxiliary device initialization could expose a partially initialized object to the release callback after an allocation failure, causing a local privileged kernel crash in a rare driver error path.

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

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

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: LOW
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-68375	LOW	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';CWE-665;**CWE-476;CWE-703;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'bnxt_en auxiliary device initialization could leave an auxiliary private object only partially initialized when an allocation failure happens after auxiliary_device_init succeeds. The release callback expects aux_priv id, aux_priv edev, edev net, and edev ulp_tbl to be valid, so the error unwind path can dereference missing state and crash the kernel. For the CVSS the PR:L is used in the paranoid score because some deployments may delegate device probing or driver control to a constrained local service account rather than full host root. Typical deployments are closer to PR:H because driver load and device management are administrative operations. The issue is not directly network reachable and is not triggered by packet traffic. Impact is denial of service via kernel crash only.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like, auto-close candidate (with actual score 1)	YES	REMOTE DANGER INIT NETWORK HARDWARE  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	YES	NO	checked

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

ActionableScore=2
ActionableScoreLower=0

## 1. ActionableScore

* Conservative score: 0
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate / Low-like, auto-close candidate**::

## 2. Signal breakdown

Conservative signals:

* Weak or indirect corruption candidate: +1
  The release callback may dereference or clear partially initialized state, but the patch does not show UAF, double free, OOB write, arbitrary write, callback hijack, or attacker-controlled object reuse.

* Reliable kernel crash / strong DoS: +1
  A NULL pointer dereference in the release path is plausible if allocation fails after auxiliary_device_init() succeeds.

* Requires admin/root/device-management control in typical deployments: -2
  The affected path is driver auxiliary device initialization and error unwind, normally reachable during driver probing, loading, device setup, or reset-like management operations.

* Hard or unreliable special condition: -1
  Triggering requires an allocation failure at a narrow point after auxiliary_device_init() and before all dependent fields are initialized.

* Conservative total floors to 0.

Paranoid signals:

* Weak or indirect corruption candidate: +1
  Partially initialized kernel object state reaches a release callback that assumes fully initialized pointers.

* Reliable kernel crash / strong DoS: +1
  The likely practical failure mode is kernel crash via NULL dereference.

* Privileged device-management lifetime path: +1
  The bug is in driver initialization and release/unwind ordering, which deserves some review because it affects object lifetime assumptions in a trusted kernel driver path.

* Hard or unreliable special condition: -1
  The failure depends on a specific allocation-failure window and is not a normal packet-processing path.

* Paranoid total: 2.

No points awarded for remote reachability, local unprivileged trigger, privilege escalation, strong memory corruption, real UAF, confidentiality impact, integrity impact, Dirty-Pipe-like behavior, or broad common data-plane exposure.

## 3. Reachability analysis

The bug is reachable during bnxt_en auxiliary device initialization, specifically if auxiliary_device_init() succeeds and a later allocation fails before aux_priv, edev, and ulp_tbl are fully populated. In normal deployments this requires administrative control over driver loading, device probing, binding, or similar device-management operations. A reduced-capability service or container with delegated device-management control could make PR effectively lower, but this is not a common unprivileged path. The issue is not network-triggerable by packet traffic and does not appear firmware-mediated from the provided patch. Realistic exploitation requires Broadcom bnxt hardware plus a narrow allocation-failure error path.

Call-site confidence: high, because the relevant initialization and unwind path is present in the patch.

## 4. Severity interpretation

This behaves like an ordinary Moderate or Low-like kernel reliability issue rather than an Important-class vulnerability. The theoretical concern is a partially initialized object reaching a release callback, but the demonstrated primitive is only NULL dereference or cleanup of incomplete state. There is no evidence of attacker-controlled reclaim, stale object reuse, write-after-free, type confusion, arbitrary write, sensitive data disclosure, or privilege escalation. The main practical impact is local privileged DoS during rare driver initialization failure handling.

## 5. One-sentence report phrase

bnxt_en auxiliary device initialization could expose a partially initialized object to the release callback after an allocation failure, causing a local privileged kernel crash in a rare driver error path.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

The issue is not remotely reachable, not unprivileged in typical deployments, and does not show a concrete memory-corruption or privilege-escalation primitive beyond a constrained NULL dereference in a driver initialization error path.

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

Patch: bnxt_en: Handle partially initialized auxiliary devices [ Upstream
Commit: 4e1caa5fdd0dea36938fe39cceb1522e9d86c937
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4e1caa5fdd0dea36938fe39cceb1522e9d86c937

Changed files:
  drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.c

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=4e1caa5fdd0dea36938fe39cceb1522e9d86c937

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

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

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:H/PR:H/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.7

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: 2

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: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

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).