Description
In the Linux kernel, the following vulnerability has been resolved:

bnxt_en: Handle partially initialized auxiliary devices

bnxt_aux_devices_init() calls auxiliary_device_init() before all fields
used by bnxt_aux_dev_release() are initialized. After
auxiliary_device_init() succeeds, later errors must unwind with
auxiliary_device_uninit(), which invokes the release callback.

The release callback assumes that aux_priv->id, aux_priv->edev,
edev->net and edev->ulp_tbl are all populated. If allocation fails
after auxiliary_device_init(), the release path can otherwise dereference
or clear partially initialized state.

Allocate and attach the bnxt_en_dev and ULP table before calling
auxiliary_device_init(), so the release callback only sees a fully
initialized auxiliary private object. If auxiliary_device_init() itself
fails, free those allocations directly because device_initialize() has not
run and the release callback will not be invoked.

This issue was found by a static analysis checker and confirmed by manual
source review.
Published: 2026-08-10
Score: 4.4 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The bnxt_en driver in the Linux kernel uses auxiliary devices. During device initialization the private structure is only partially populated before auxiliary_device_init() succeeds, and if later steps fail the release callback attempts to access fields that may be NULL or uninitialized. This can lead to null pointer dereference or memory corruption within kernel context, causing a kernel panic or crash. The vulnerability allows a privileged attacker to degrade system availability by triggering a failure path during device initialization or by directly manipulating the driver to simulate allocation failures.

Affected Systems

Linux kernel installations that include the bnxt_en network driver are potentially affected. No specific kernel versions are listed, so any recent kernel build that ships with the bnxt_en module could be vulnerable until the patch is applied.

Risk and Exploitability

The EPSS score is < 1%, and the vulnerability is not currently listed in CISA KEV. The CVSS score is 4.4, indicating a moderate severity, but the kernel panic outcome still represents a significant denial-of-service risk. Exploitation requires the ability to load the bnxt_en device or to induce a failure during its initialization, which typically needs privileged access or physical control of the hardware. The attack vector is inferred to be local with kernel privileges; denial of service is the primary risk.

Generated by OpenCVE AI on August 12, 2026 at 18:45 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the latest Linux kernel update that includes the bnxt_en_driver fix for partial initialization
  • If an update is not available, disable or unload the bnxt_en device to prevent the vulnerable code from executing
  • Ensure the system kernel is configured to use the latest stable release and verify that bnxt_en is not loaded on any vulnerable hardware

Generated by OpenCVE AI on August 12, 2026 at 18:45 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 12 Aug 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-824
References
Metrics threat_severity

None

cvssV3_1

{'score': 4.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate


Mon, 10 Aug 2026 16:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-476
CWE-665

Mon, 10 Aug 2026 12:30:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Handle partially initialized auxiliary devices bnxt_aux_devices_init() calls auxiliary_device_init() before all fields used by bnxt_aux_dev_release() are initialized. After auxiliary_device_init() succeeds, later errors must unwind with auxiliary_device_uninit(), which invokes the release callback. The release callback assumes that aux_priv->id, aux_priv->edev, edev->net and edev->ulp_tbl are all populated. If allocation fails after auxiliary_device_init(), the release path can otherwise dereference or clear partially initialized state. Allocate and attach the bnxt_en_dev and ULP table before calling auxiliary_device_init(), so the release callback only sees a fully initialized auxiliary private object. If auxiliary_device_init() itself fails, free those allocations directly because device_initialize() has not run and the release callback will not be invoked. This issue was found by a static analysis checker and confirmed by manual source review.
Title bnxt_en: Handle partially initialized auxiliary devices
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-17T05:04:20.877Z

Reserved: 2026-07-30T09:28:09.386Z

Link: CVE-2026-68375

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-10T13:20:30.423

Modified: 2026-08-17T06:17:45.900

Link: CVE-2026-68375

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-08-10T12:03:53Z

Links: CVE-2026-68375 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-12T19:00:08Z

Weaknesses
  • CWE-476

    NULL Pointer Dereference

  • CWE-665

    Improper Initialization

  • CWE-824

    Access of Uninitialized Pointer