CVE-2026-98535

Description

A flaw was found in the Linux kernel's Freescale Frame Manager (fman) network driver. During device initialization, the driver retrieves a system clock resource to check its frequency but fails to release the reference count after reading the value. This omission results in a resource leak, preventing the clock object from being properly freed and potentially causing resource exhaustion.

Statement

This vulnerability is rated as Low severity because triggering the issue requires specialized hardware and elevated privileges, limiting both applicability and operational impact. The affected network driver is specific to Freescale/NXP architectures and is not utilized in standard enterprise deployments. Furthermore, the clock reference imbalance occurs solely during device probe and node initialization rather than regular runtime operations, preventing unprivileged users from generating recurring leaks or causing system instability.

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 Score2.3N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredHighN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactLowN/AN/A

Vector

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

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Resource Consumption (Other); DoS: Resource Consumption (Memory); DoS: Resource Consumption (CPU)

An attacker that can influence the allocation of resources that are not properly released could deplete the available resource pool and prevent all other processes from accessing the same type of resource. Frequently-affected resources include memory, CPU, disk space, power or battery, etc.

Frequently Asked Questions

Want to get errata notifications? Sign up here.