CVE-2026-68375
Last modified
CVE-2026-68375 is a vulnerability of currently unknown severity. 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.
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.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 194fad5b27815ca80e832ac875c0026ff96fc243, < 4e1caa5fdd0dea36938fe39cceb1522e9d86c937; >= 194fad5b27815ca80e832ac875c0026ff96fc243, < 1cb8553c02e93e5a150cebd42f9ee3db0ece4707 |
| Linux | Linux | 6.10 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-68375?
How severe is CVE-2026-68375?
How do I fix CVE-2026-68375?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-6837A post-authentication command injection vulnerability in the…7.2
- CVE-2026-68370In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68371In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68372In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68373In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68374In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68376In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68377In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68378In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68379In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68380In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68381In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-68375?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
