VDB

CVE-2026-68375

CVE-2026-68375 PUBLISHED

bnxt_en: Handle partially initialized auxiliary devices

Reported by linux · Published August 10, 2026

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.

EPSS 0.18% · 7.1th percentile

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
LinuxLinux4e1caa5fdd0dea36938fe39cceb1522e9d86c937, 1cb8553c02e93e5a150cebd42f9ee3db0ece4707

Risk scores

EPSS Score
0.18%
7.1th percentile

Affected products

VendorProductVersions
LinuxLinux194fad5b27815ca80e832ac875c0026ff96fc243, 194fad5b27815ca80e832ac875c0026ff96fc243, 194fad5b27815ca80e832ac875c0026ff96fc243
LinuxLinux6.10, 0, 6.12.114
LinuxLinux6.12.114, 7.2, 194fad5b27815ca80e832ac875c0026ff96fc243
linuxlinux_kernel6.10, 6.10, 6.10

Timeline

  • Aug 10, 2026 Coalition ESS Score
  • Aug 10, 2026 CVE Published
  • Aug 16, 2026 Security Advisory
  • Aug 24, 2026 EPSS Score (15 in total, the first dated here)
  • Oct 21, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2026-68375
vulnetix vdb fixes CVE-2026-68375

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-68375/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›