CVE-2026-98826

Description

A flaw was found in the Linux kernel's AC100 Real-Time Clock (RTC) driver. If device initialization fails during driver probing, unmanaged clock provider references remain registered in global system lists while their underlying memory is released. Subsequent lookups referencing the affected device can access this freed memory, triggering a use-after-free condition that can lead to a system crash and Denial of Service (DoS).

Statement

The AC100 RTC probe failure path can leave an OF clock provider registered after its device managed chip clk_data object has been freed. A later clock lookup for the same device tree node passes the dangling object to of_clk_hw_onecell_get, which reads freed num and hws fields and can return a stale clk_hw pointer to a consumer. The demonstrated primitive is a use-after-free read with a likely kernel crash or device initialization failure. A more serious consequence cannot be excluded because the freed object contains pointers that may be used by the clock subsystem after memory reuse. For the CVSS the PR:L value is used for the paranoid score because a local user may contribute to the required memory pressure without controlling the device directly, although reliable triggering normally requires an ENOMEM failure during probe and a later clock lookup. AC:H reflects this narrow timing and state requirement. The issue is not network reachable and affects systems with the AC100 RTC and a matching device tree clock consumer. Impact is at least local denial of service and the stale pointer path may allow confidentiality or integrity impact if the freed allocation is reused in a controllable way.

Mitigation

Mitigation for this issue is either not available or the currently available options don't 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 Score4.7N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/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:H/PR:L/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Confidentiality

Technical Impact: Read Memory

Read operations on freed memory can sometimes leak sensitive information instead of causing a crash

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Frequently Asked Questions

Want to get errata notifications? Sign up here.