CVE-2024-50189

Description

A flaw was found in the Linux kernel's AMD Sensor Fusion Hub (SFH) Human Interface Device (HID) driver. Improper memory cleanup during the device's initialization process can lead to memory errors and system instability. A local attacker with low privileges could exploit this to trigger page faults, cause the Btrfs file system to become read-only, or lead to Btrfs disk corruption, effectively causing a Denial of Service (DoS) and potential data loss.

Mitigation

To mitigate this issue, prevent the `amd_sfh` kernel module from loading by blacklisting it. This can be achieved by creating a modprobe configuration file.

1. Create a file named `/etc/modprobe.d/blacklist-amd_sfh.conf` with the following content:

   blacklist amd_sfh
2. Regenerate the initramfs to ensure the blacklist is applied during boot:
bash
sudo dracut -f -v
# OR for Ubuntu/Debian based systems:
# sudo update-initramfs -u
3. Reboot the system for the changes to take effect.

This mitigation may impact functionality that relies on the AMD Sensor Fusion Hub. A system reboot is required for the changes to take effect.

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).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score4.45.57.8
Attack VectorLocalLocalLocal
Attack ComplexityLowLowLow
Privileges RequiredHighLowLow
User InteractionNoneNoneNone
ScopeUnchangedUnchangedUnchanged
ConfidentialityNoneNoneHigh
Integrity ImpactNoneNoneHigh
Availability ImpactHighHighHigh

Vector

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

NVD: 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)

Availability,Other

Technical Impact: DoS: Resource Consumption (Other); Varies by Context

Most unreleased resource issues result in general software reliability problems, but if an attacker can intentionally trigger a resource leak, the attacker might be able to launch a denial of service attack by depleting the resource pool.

Confidentiality

Technical Impact: Read Application Data

When a resource containing sensitive information is not correctly shutdown, it may expose the sensitive data in a subsequent allocation.

Frequently Asked Questions

Want to get errata notifications? Sign up here.