CVE-2022-49474

Description

A flaw was discovered in the Linux kernel’s Bluetooth subsystem, SCO sockets. When calling sco_sock_connect() and connecting the same socket twice in quick succession, two sco_conn objects may be created, but only one gets associated with the socket. If the socket is closed before the SCO connection is fully established, the timer linked to the dangling sco_conn is not canceled. This results in a use-after-free issue in sco_sock_timeout(), where the kernel attempts to access the freed socket. A local, unprivileged user may exploit this flaw to trigger kernel memory corruption, resulting in system instability or a denial of service.

Statement

Red Hat has assigned this vulnerability a Moderate severity rating with a CVSS score of 5.5. This assessment is based on the following key factors:

  • It is impossible to create sco_conn objects without physical access to both the server and client systems.
  • The dangling timer can cause a resource consumption attack, but there is no risk of any data leaks.
  • There is no loss of integrity, as even in case of successful exploitation, there is no data exchanged between the client and the server.

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 Score5.5N/A7.8
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: 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)

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.