CVE-2026-98640

Description

A flaw was found in the Linux kernel's AMD Sensor Fusion Hub (amd_sfh) driver. An attacker capable of attaching or emulating a crafted Peripheral Component Interconnect (PCI) device can cause a Denial of Service (DoS) through a system crash. This issue occurs because the driver fails to validate the PCI Base Address Register (BAR) size before accessing device registers, leading to an out-of-bounds memory read during device initialization.

Statement

This vulnerability is rated as having Moderate impact for Red Hat Enterprise Linux because exploitation requires privileged access or physical presence to connect a specially crafted or emulated PCI device. An attacker cannot trigger the condition remotely or without elevated privileges capable of manipulating hardware interfaces. In typical Red Hat deployments, systems are not exposed to untrusted PCI devices, and successful exploitation results strictly in a denial of service through a kernel panic during device probing, without integrity or confidentiality loss.

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.4N/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 ImpactHighN/AN/A

Vector

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

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.

Confidentiality

Technical Impact: Bypass Protection Mechanism

Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.

Other

Technical Impact: Varies by Context

The read operation could produce other undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.