CVE-2024-36032

Description

A flaw was found in the Linux kernel's Qualcomm Atheros Bluetooth (QCA) driver. Due to missing validation checks when retrieving firmware build identifiers, a malformed response can leave uninitialized memory in a buffer exposed through the debug filesystem (debugfs). A local user with access to debugfs could exploit this flaw to inspect sensitive kernel stack contents, leading to information disclosure.

Statement

This vulnerability is rated as having Low severity for Red Hat because successful exploitation requires local administrative access to debugfs and the presence of physical Qualcomm Atheros Bluetooth hardware. The exposure is limited to disclosing uninitialized kernel memory without granting privilege escalation or causing a denial of service. Additionally, debugfs access is restricted to root by default across Red Hat Enterprise Linux deployments, substantially constraining unprivileged attack vectors.

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.37.18.1
Attack VectorLocalLocalAdjacent Network
Attack ComplexityLowLowLow
Privileges RequiredHighLowNone
User InteractionNoneNoneNone
ScopeUnchangedUnchangedUnchanged
ConfidentialityNoneHighHigh
Integrity ImpactLowNoneNone
Availability ImpactNoneHighHigh

Vector

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

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

cve.org: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/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.