Linux Kernel up to 5.18.2 sco_sock_connect use after free

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.6$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Linux Kernel up to 5.18.2. Affected by this issue is the function sco_sock_connect. This manipulation causes use after free. This vulnerability is tracked as CVE-2022-49474. No exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability has been found in Linux Kernel up to 5.18.2 and classified as critical. Affected by this vulnerability is the function sco_sock_connect. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout Connecting the same socket twice consecutively in sco_sock_connect() could lead to a race condition where two sco_conn objects are created but only one is associated with the socket. If the socket is closed before the SCO connection is established, the timer associated with the dangling sco_conn object won't be canceled. As the sock object is being freed, the use-after-free problem happens when the timer callback function sco_sock_timeout() accesses the socket. Here's the call trace: dump_stack+0x107/0x163 ? refcount_inc+0x1c/ print_address_description.constprop.0+0x1c/0x47e ? refcount_inc+0x1c/0x7b kasan_report+0x13a/0x173 ? refcount_inc+0x1c/0x7b check_memory_region+0x132/0x139 refcount_inc+0x1c/0x7b sco_sock_timeout+0xb2/0x1ba process_one_work+0x739/0xbd1 ? cancel_delayed_work+0x13f/0x13f ? __raw_spin_lock_init+0xf0/0xf0 ? to_kthread+0x59/0x85 worker_thread+0x593/0x70e kthread+0x346/0x35a ? drain_workqueue+0x31a/0x31a ? kthread_bind+0x4b/0x4b ret_from_fork+0x1f/0x30

It is possible to read the advisory at git.kernel.org. This vulnerability is known as CVE-2022-49474 since 02/26/2025. The exploitation appears to be easy. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/28/2025).

The vulnerability scanner Nessus provides a plugin with the ID 240793 (SUSE SLES12 Security Update : kernel (SUSE-SU-2025:01983-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.9.318, 4.14.283, 4.19.247, 5.4.198, 5.10.121, 5.15.46, 5.17.14 or 5.18.3 eliminates this vulnerability. Applying the patch 9de3dc09e56f8deacd2bdbf4cecb71e11a312405/7d61dbd7311ab978d8ddac1749a758de4de00374/390d82733a953c1fabf3de9c9618091a7a9c90a6/6f55fac0af3531cf60d11369454c41f5fc81ab3f/36c644c63bfcaee2d3a426f45e89a9cd09799318/65d347cb39e2e6bd0c2a745ad7c928998ebb0162/537f619dea4e3fa8ed1f8f938abffe3615794bcc/99df16007f4bbf9abfc3478cb17d10f0d7f8906e/7aa1e7d15f8a5b65f67bacb100d8fc033b21efa2 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (240793). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.0
VulDB Meta Temp Score: 7.6

VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 240793
Nessus Name: SUSE SLES12 Security Update : kernel (SUSE-SU-2025:01983-1)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Kernel 4.9.318/4.14.283/4.19.247/5.4.198/5.10.121/5.15.46/5.17.14/5.18.3
Patch: 9de3dc09e56f8deacd2bdbf4cecb71e11a312405/7d61dbd7311ab978d8ddac1749a758de4de00374/390d82733a953c1fabf3de9c9618091a7a9c90a6/6f55fac0af3531cf60d11369454c41f5fc81ab3f/36c644c63bfcaee2d3a426f45e89a9cd09799318/65d347cb39e2e6bd0c2a745ad7c928998ebb0162/537f619dea4e3fa8ed1f8f938abffe3615794bcc/99df16007f4bbf9abfc3478cb17d10f0d7f8906e/7aa1e7d15f8a5b65f67bacb100d8fc033b21efa2

Timelineinfo

02/26/2025 🔍
02/26/2025 +0 days 🔍
02/26/2025 +0 days 🔍
06/28/2025 +122 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2022-49474 (🔍)
GCVE (CVE): GCVE-0-2022-49474
GCVE (VulDB): GCVE-100-297067

Entryinfo

Created: 02/26/2025 10:06
Updated: 06/28/2025 04:07
Changes: 02/26/2025 10:06 (58), 03/25/2025 02:42 (1), 06/28/2025 04:07 (2)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Might our Artificial Intelligence support you?

Check our Alexa App!