LiveActive security incident?Get immediate response
CVE Record

CVE-2025-21743: usbnet: ipheth: fix possible overflow in DPE length check

In the Linux kernel, the following vulnerability has been resolved: usbnet: ipheth: fix possible overflow in DPE length check Originally, it was possible for the DPE length check to overflow if wDatagramIndex + wDatagramLength > U16_MAX. This could lead to an OoB read. Move the wDatagramIndex term to the other side of the inequality. An existing condition ensures that wDatagramIndex < urb->actual_length.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-21743 is a Linux kernel flaw in the usbnet ipheth driver. A bad length calculation can overflow and cause the kernel to read outside the expected buffer. Business risk is highest for Linux systems where this driver is present and reachable through local use or attached USB networking paths.

Executive priority

Treat as high priority for Linux endpoint, appliance, and device fleets with USB networking exposure. It is not currently evidenced as exploited here, but kernel out-of-bounds reads can affect confidentiality and availability.

Technical view

The ipheth DPE length check could overflow when wDatagramIndex plus wDatagramLength exceeds U16_MAX, creating an out-of-bounds read condition. The stated fix moves wDatagramIndex to the other side of the inequality. The issue is classified as CWE-125 with CVSS 3.1 score 7.1.

Likely exposure

Exposure is likely limited to Linux systems with affected kernel builds and the usbnet ipheth driver present or usable. The provided version data is not a complete distro matrix, so vendor kernel advisories and backport status must be checked.

Exploitation context

The bundle does not show CISA KEV listing, and no provided source reports active exploitation. CVSS marks the attack vector as local, low complexity, low privilege, no user interaction, with high confidentiality and availability impact.

Researcher notes

The evidence identifies the vulnerable logic and upstream stable commits, but affected-version metadata is sparse and partly ambiguous. Avoid assuming distro exposure from upstream versions alone; confirm with vendor backport records and local kernel configuration.

Mitigation direction

  • Update to a Linux kernel containing the referenced stable fix commits.
  • Check distribution advisories for backported fixes before relying on upstream version numbers.
  • Restrict untrusted local USB/network-device access where operationally feasible.
  • Track vendor guidance if running appliance, embedded, or custom kernels.

Validation and detection

  • Inventory Linux kernel versions across servers, endpoints, and appliances.
  • Check whether the ipheth driver is built, loaded, or available.
  • Map installed kernels against distro advisories and the cited stable commits.
  • Confirm patched kernels are running after maintenance reboots.
Prepared
Confidence
medium
Sources
6

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.

cwe · low confidence lookup

CWE-125: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-21743 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
7.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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
1ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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
7.1CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H1.85.2CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxa2d274c62e44b1995c170595db3865c6fe701226, a2d274c62e44b1995c170595db3865c6fe701226, a2d274c62e44b1995c170595db3865c6fe701226, a2d274c62e44b1995c170595db3865c6fe701226unaffected
LinuxLinux6.5, 0, 6.6.78, 6.12.14, 6.13.3, 6.14affected
Weakness

CWE details

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

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.