CVE-2026-89441

Description

A flaw was found in the Linux kernel, specifically within the mmc: via-sdmmc driver responsible for managing SD and MultiMediaCard (MMC) devices. This vulnerability occurs during device removal, where a timing issue allows a process to attempt to access memory that has already been released. This unauthorized memory access can lead to system instability or cause the system to crash, resulting in a denial of service.

Statement

A moderate-severity use-after-free flaw was found in the Linux kernel VIA SD/MMC host controller driver (mmc: via-sdmmc), which affects Red Hat offerings that ship a Linux kernel containing this driver code. During device removal, disabling the device interrupt and freeing the IRQ prevents new card-detect work from being queued, but card-detect work already queued by the handler (carddet_work) can still run after via_sd_remove() returns. via_sdc_card_detect() recovers the host structure through container_of() and dereferences its MMIO base, so once remove() returns and the host can be freed, that work touches freed memory. A local attacker with low privileges able to trigger removal of the VIA SD/MMC PCI device could exploit this race to crash the kernel, causing a denial of service; confidentiality and integrity are not affected. Red Hat rates this flaw Moderate (CVSS 5.5, CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) because it requires local access on systems with the affected hardware and impacts availability only. This differs from the upstream severity of Important (CVSS 7.8), which also scores high confidentiality and integrity impacts: the technical evidence shows the consequence is limited to touching freed kernel memory, which can crash the system.

Mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

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/A7.8
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

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

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

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.

Frequently Asked Questions

Want to get errata notifications? Sign up here.