# CVE-2026-43034: bnxt_en: set backing store type from query type

> Incorrect backing store type assignment in the bnxt_en driver could lead to undefined behavior or memory access issues.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 May 2026
- **Updated:** 21 Oct 2026
- **Also known as:** BELL-CVE-2026-43034, DEBIAN-CVE-2026-43034, GHSA-w54w-gcfv-p884, ROOT-OS-DEBIAN-13-CVE-2026-43034, ROOT-OS-UBUNTU-2404-CVE-2026-43034, UBUNTU-CVE-2026-43034

## What is CVE-2026-43034?

CVE-2026-43034 is a medium-severity vulnerability in Linux kernel, published on 1 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

bnxt_en: set backing store type from query type

bnxt_hwrm_func_backing_store_qcaps_v2() stores resp->type from the
firmware response in ctxm->type and later uses that value to index
fixed backing-store metadata arrays such as ctx_arr[] and
bnxt_bstore_to_trace[].

ctxm->type is fixed by the current backing-store query type and matches
the array index of ctx->ctx_arr. Set ctxm->type from the current loop
variable instead of depending on resp->type.

Also update the loop to advance type from next_valid_type in the for
statement, which keeps the control flow simpler for non-valid and
unchanged entries.

## Which versions are affected by CVE-2026-43034?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-43034?

Apply the vendor's patch.

## Is CVE-2026-43034 being exploited?

There is no known exploitation of CVE-2026-43034 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-43034 and fix it if it is affected.

What it is: CVE-2026-43034 is a medium-severity vulnerability in Linux kernel, published on 1 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-43034 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-43034/ (Markdown: https://insights.sbomify.com/CVE-2026-43034/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-43034
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-43034
- OSV: https://osv.dev/vulnerability/CVE-2026-43034

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-43034/
Summaries are generated and may contain mistakes; the official description above is the record.