LiveActive security incident?Get immediate response
CVE Record

CVE-2025-21800: net/mlx5: HWS, fix definer's HWS_SET32 macro for negative offset

In the Linux kernel, the following vulnerability has been resolved: net/mlx5: HWS, fix definer's HWS_SET32 macro for negative offset When bit offset for HWS_SET32 macro is negative, UBSAN complains about the shift-out-of-bounds: UBSAN: shift-out-of-bounds in drivers/net/ethernet/mellanox/mlx5/core/steering/hws/definer.c:177:2 shift exponent -8 is negative

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel bug in the Mellanox/NVIDIA mlx5 networking driver. A negative bit offset can trigger undefined shift behavior reported by UBSAN. The public record does not provide CVSS, business impact, or exploitation evidence, so treat it as a kernel maintenance issue until vendor guidance says otherwise.

Executive priority

Handle through normal kernel patch management, with higher priority for infrastructure using mlx5 networking. Current public evidence does not justify emergency treatment, but kernel defects in network drivers deserve timely remediation.

Technical view

The resolved issue is in net/mlx5 HWS definer logic, where HWS_SET32 can shift with a negative exponent, producing a UBSAN shift-out-of-bounds report in drivers/net/ethernet/mellanox/mlx5/core/steering/hws/definer.c.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions or commits with the mlx5 driver path present. Systems without Mellanox/NVIDIA mlx5 networking hardware or driver usage are less likely to encounter this code path, but the source bundle does not define exact runtime prerequisites.

Exploitation context

The supplied sources do not show active exploitation, public exploit availability, or CISA KEV listing. They also do not state whether the issue is reachable by remote traffic, local users, or only specific driver configuration paths.

Researcher notes

Key gaps are impact, reachability, and affected configuration detail. The strongest evidence is the Linux kernel resolution text and stable commit references; avoid assuming privilege impact, denial of service, or remote reachability without vendor confirmation.

Mitigation direction

  • Check your Linux vendor advisory for CVE-2025-21800 applicability.
  • Apply kernel updates containing the referenced stable fixes.
  • Prioritize systems using mlx5 networking hardware or drivers.
  • If patching is delayed, ask the vendor for supported mitigations.

Validation and detection

  • Inventory running kernel versions across Linux hosts.
  • Identify hosts with mlx5 hardware, modules, or driver packages.
  • Check changelogs for CVE-2025-21800 or the referenced commits.
  • Review kernel logs for UBSAN shift-out-of-bounds reports in mlx5 definer.c.
Prepared
Confidence
medium
Sources
5

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-21800 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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux74a778b4a63faef9ff02aad0d332b209835f93e1, 74a778b4a63faef9ff02aad0d332b209835f93e1, 74a778b4a63faef9ff02aad0d332b209835f93e1unaffected
LinuxLinux6.12, 0, 6.12.13, 6.13.2, 6.14affected
Weakness

CWE details

No CWE listed

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