# CVE-2025-68197: bnxt_en: Fix null pointer dereference in bnxt_bs_trace_check_wrap()

> A null pointer dereference in the bnxt_en driver can cause a kernel crash, leading to denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-68197, DEBIAN-CVE-2025-68197, GHSA-x9w6-jqxg-cp95, UBUNTU-CVE-2025-68197

## What is CVE-2025-68197?

CVE-2025-68197 is a vulnerability in Linux, published on 16 Dec 2025. 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: Fix null pointer dereference in bnxt_bs_trace_check_wrap()

With older FW, we may get the ASYNC_EVENT_CMPL_EVENT_ID_DBG_BUF_PRODUCER
for FW trace data type that has not been initialized.  This will result
in a crash in bnxt_bs_trace_type_wrap().  Add a guard to check for a
valid magic_byte pointer before proceeding.

## Which versions are affected by CVE-2025-68197?


## How do I fix CVE-2025-68197?

Apply the vendor's patch.

## Is CVE-2025-68197 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68197 and fix it if it is affected.

What it is: CVE-2025-68197 is a vulnerability in Linux, published on 16 Dec 2025. 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-2025-68197 in the wild and no public exploit code.

Affected product: Linux. 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-2025-68197/ (Markdown: https://insights.sbomify.com/CVE-2025-68197/index.md)
```

## Sources

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

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