# bnxt: Do not read past the end of test names

CVE record · `CVE-2023-53010`

- **Identifiers:** `CVE-2023-53010`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 27 Mar 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 27 Mar 2025, 16:43 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `eb51365846bc418687af4c4f41b68b6e84cdd449 to before cefa85480ac99c0bef5a09daadb48d65fc28e279` (git)
  - affected: `eb51365846bc418687af4c4f41b68b6e84cdd449 to before d3e599c090fc6977331150c5f0a69ab8ce87da21` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.12`
  - unaffected: `before 4.12` (semver)
  - unaffected: `6.1.9 to 6.1.*, inclusive` (semver)
  - unaffected: `6.2 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel bnxt driver from 4.12 before the fixes read past the end of test names during ethtool initialization, which tripped buffer overflow detection. The source gives few details on what an attacker needs or can do. Upgrade to 6.1.9 or later in the 6.1 series, or to 6.2 or later.

Written 16 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0019, the 9th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 27 Mar 2025, 16:43 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2023-53010)
- 27 Mar 2025, 17:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2023-53010)

## Sources

- [CVE List: CVE-2023-53010](https://www.cve.org/CVERecord?id=CVE-2023-53010)
- [NVD: CVE-2023-53010](https://nvd.nist.gov/vuln/detail/CVE-2023-53010)

### References from the CNA

- <https://git.kernel.org/stable/c/cefa85480ac99c0bef5a09daadb48d65fc28e279>
- <https://git.kernel.org/stable/c/d3e599c090fc6977331150c5f0a69ab8ce87da21>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2023-53010>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2023-53010/>. Everything for agents: <https://agentprime.io/llms.txt>.
