CVE-2026-99720

Description

A flaw was found in the Linux kernel's ChipCap 2 hardware monitoring driver. This vulnerability can result in a denial of service (DoS) via a kernel crash. During driver teardown, interrupt request (IRQ) handlers are released after the monitoring device has already been unregistered and freed. This improper cleanup sequence allows an interrupt handler to access freed memory, causing a use-after-free condition when a local user unloads the driver or disconnects the device.

Statement

This vulnerability is rated as having Moderate impact because triggering the condition requires local administrative privileges, precise timing during driver teardown, and the presence of specialized physical hardware. The flaw resides in the Amphenol ChipCap 2 sensor driver, which is not utilized in typical server environments unless the specific sensor is attached. Consequently, the blast radius is constrained to a local denial of service (system crash) on systems equipped with this hardware.

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.1N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredHighN/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:H/UI:N/S:U/C:N/I:N/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.