LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22112: eth: bnxt: fix out-of-range access of vnic_info array

In the Linux kernel, the following vulnerability has been resolved: eth: bnxt: fix out-of-range access of vnic_info array The bnxt_queue_{start | stop}() access vnic_info as much as allocated, which indicates bp->nr_vnics. So, it should not reach bp->vnic_info[bp->nr_vnics].

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel bug in the bnxt Ethernet driver where code can access one entry past the allocated vnic_info array. The public record does not provide CVSS, impact details, or an exploitation claim, so business urgency depends on whether your Linux systems use this driver and affected kernel builds.

Executive priority

Treat this as a targeted kernel maintenance item, not a confirmed emergency. Prioritize critical Linux hosts using bnxt networking, especially where downtime from kernel instability would materially affect operations.

Technical view

The resolved issue is an out-of-range access in bnxt_queue_start() or bnxt_queue_stop(), which can reach bp->vnic_info[bp->nr_vnics] even though vnic_info is allocated only up to bp->nr_vnics entries. The available sources identify Linux kernel fixes in stable commits but do not describe trigger conditions or impact.

Likely exposure

Likely exposure is limited to Linux systems with the bnxt Ethernet driver in affected kernel versions or commit ranges. The source bundle does not name distributions, appliances, cloud images, or hardware SKUs, so confirm exposure through local kernel and driver inventory.

Exploitation context

CISA KEV status is false in the source bundle, and no cited source states active exploitation. The public information provided does not describe a practical attack path, required privileges, or whether the condition is remotely reachable.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploit status, or impact class is provided. The core defect is a bounds issue in bnxt vnic_info indexing. Researchers should avoid assuming reachability or severity without analyzing the fixed commits and affected call paths.

Mitigation direction

  • Check Linux vendor or distribution advisories for backported fixes.
  • Update affected kernels to fixed vendor-supported releases when available.
  • Prioritize systems where the bnxt driver is present or loaded.
  • Use the referenced stable commits to confirm whether a custom kernel includes the fix.

Validation and detection

  • Inventory kernel versions on Linux systems using bnxt networking.
  • Confirm whether the bnxt driver is present, loaded, or built into custom kernels.
  • Compare deployed kernels against vendor advisories and referenced stable commits.
  • Review crash or kernel warning telemetry for bnxt driver instability.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-22112 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxa6604717850e4c0fe39bd6084cfbc1bfc445d2b5, 661958552eda5bf64bfafb4821cbdded935f1f68, 661958552eda5bf64bfafb4821cbdded935f1f68, b730dcab64d5f113af347cf8de696dab6ce88542, 6.12.20, 6.13.8unaffected
LinuxLinux6.14, 0, 6.12.35, 6.14.2, 6.15affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.