CVE-2022-49474

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.

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.

The CVSS score(s) listed for this vulnerability do not reflect the associated product's status, and are included for informational purposes to better understand the severity of this vulnerability.