LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22108: bnxt_en: Mask the bd_cnt field in the TX BD properly

In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Mask the bd_cnt field in the TX BD properly The bd_cnt field in the TX BD specifies the total number of BDs for the TX packet. The bd_cnt field has 5 bits and the maximum number supported is 32 with the value 0. CONFIG_MAX_SKB_FRAGS can be modified and the total number of SKB fragments can approach or exceed the maximum supported by the chip. Add a macro to properly mask the bd_cnt field so that the value 32 will be properly masked and set to 0 in the bd_cnd field. Without this patch, the out-of-range bd_cnt value will corrupt the TX BD and may cause TX timeout. The next patch will check for values exceeding 32.

HighCVSS 8.6Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux network-driver flaw can corrupt a transmit descriptor when a packet uses an unusually high number of fragments. The resulting transmission timeout may disrupt network availability. The supplied CVSS score is 8.6, but the sources do not establish a practical remote attack path or observed exploitation.

Executive priority

Treat as a high-priority availability risk for network-critical Linux hosts using bnxt_en. Confirm exposure promptly and patch through supported distribution channels. Systems not using this driver are unlikely to be affected by the described flaw.

Technical view

The bnxt_en driver writes the packet’s total buffer-descriptor count into a five-bit bd_cnt field, where 32 must be encoded as zero. Without proper masking, an out-of-range fragment count can corrupt the transmit buffer descriptor and cause a TX timeout. The supplied commits correct the masking behavior.

Likely exposure

Exposure is limited to Linux systems using the bnxt_en driver where CONFIG_MAX_SKB_FRAGS and packet fragmentation can approach or exceed the hardware limit. The supplied affected-version data is ambiguous, so distribution kernels and backports require vendor-specific confirmation.

Exploitation context

The CVE is not listed as CISA KEV in the supplied bundle, and no cited source reports active exploitation. Although the CVSS vector uses network attack complexity, the available evidence does not demonstrate that an unauthenticated remote attacker can reliably trigger the condition.

Researcher notes

The supplied version entries are internally unclear, including isolated values and a duplicated commit identifier marked unaffected. Researchers should rely on kernel commit ancestry and distribution backport records rather than version strings alone. A subsequent bounds check is mentioned, but its availability and relationship to complete remediation are not established here.

Mitigation direction

  • Install a vendor-supported kernel containing the referenced fix or an equivalent backport.
  • Check Linux distribution security guidance for exact fixed package versions.
  • Review non-default CONFIG_MAX_SKB_FRAGS settings that may increase exposure.
  • Prioritize network-critical systems using bnxt_en until their fix status is confirmed.

Validation and detection

  • Inventory systems actively using the bnxt_en network driver.
  • Record kernel and distribution package versions for affected hosts.
  • Confirm the referenced correction or an equivalent vendor backport is present.
  • Review logs and interface telemetry for TX timeouts or transmission stalls.
  • Re-test network transmission stability after updating the kernel.
Prepared
Confidence
medium
Sources
4

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-22108 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
High
CVSS
8.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

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.

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.6CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H3.94.7Linux

Vulnerability scoring details

Base CVSS 3.1 score

8.6High
CVSS 3.1 vector shape for CVE-2025-22108Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux3948b05950fdd64002a5f182c65ba5cf2d53cf71, 3948b05950fdd64002a5f182c65ba5cf2d53cf71unaffected
LinuxLinux6.4, 0, 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.