CVE-2025-40294

Description

A flaw was found in the Linux kernel's Bluetooth management (MGMT) subsystem. A local attacker could exploit an out-of-bounds (OOB) write vulnerability in the parse_adv_monitor_pattern() function. This occurs when user-controlled input for the length variable exceeds the buffer's capacity during a copy operation, potentially leading to information disclosure and a denial of service (DoS).

Statement

This vulnerability is rated as Moderate severity for Red Hat Enterprise Linux because exploitation is confined to local authenticated users who have access to the kernel Bluetooth management subsystem. In typical enterprise server and cloud environments, Bluetooth hardware is not present or enabled, significantly minimizing exposure. Successful exploitation requires specific interaction with advertisement monitoring routines, which could allow a local attacker to cause a denial of service or access sensitive kernel memory.

Mitigation

To mitigate this issue, the `bluetooth` kernel module can be prevented from loading. Create a file `/etc/modprobe.d/disable-bluetooth.conf` with the content `blacklist bluetooth`. Then, regenerate the initramfs using `dracut -f -v` and reboot the system for the changes to take effect. This mitigation will disable all Bluetooth functionality on the system.

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