CVE-2025-68790

Description

A use-after-free vulnerability was found in the Mellanox mlx5 driver in the Linux kernel. The HCA_PORTS devcom component is not cleared from device private data after being unregistered during LAG teardown. When PCI error recovery triggers two passes through mlx5_unload_one(), the second pass attempts to unregister an already-freed component, causing a use-after-free and kernel panic.

Statement

This vulnerability primarily affects s390 systems with Mellanox network adapters where PCI error recovery events trigger multiple unload passes. The issue requires specific error recovery timing conditions to manifest. While the use-after-free causes a kernel panic, the attack surface is limited to systems experiencing PCI-level errors.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.5N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

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

Understanding the Weakness (CWE)

Integrity,Confidentiality,Availability

Technical Impact: Modify Application Data; Modify Memory; DoS: Crash, Exit, or Restart; Execute Unauthorized Code or Commands

It may be possible to cause data corruption and possibly execute arbitrary code by modifying global variables or data structures at unexpected times, violating the assumptions of code that uses this global data.

Access Control

Technical Impact: Gain Privileges or Assume Identity

If a signal handler interrupts code that is executing with privileges, it may be possible that the signal handler will also be executed with elevated privileges, possibly making subsequent exploits more severe.

Frequently Asked Questions

Want to get errata notifications? Sign up here.