Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2024-50044 | First vendor Publication | 2024-10-21 |
| Vendor | Cve | Last vendor Modification | 2024-11-08 |
Security-Database Scoring CVSS v3
| Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L | |||
|---|---|---|---|
| Overall CVSS Score | 3.3 | ||
| Base Score | 3.3 | Environmental Score | 3.3 |
| impact SubScore | 1.4 | Temporal Score | 3.3 |
| Exploitabality Sub Score | 1.8 | ||
| Attack Vector | Local | Attack Complexity | Low |
| Privileges Required | Low | User Interaction | None |
| Scope | Unchanged | Confidentiality Impact | None |
| Integrity Impact | None | Availability Impact | Low |
| Calculate full CVSS 3.0 Vectors scores | |||
Security-Database Scoring CVSS v2
| Cvss vector : | |||
|---|---|---|---|
| Cvss Base Score | N/A | Attack Range | N/A |
| Cvss Impact Score | N/A | Attack Complexity | N/A |
| Cvss Expoit Score | N/A | Authentication | N/A |
| Calculate full CVSS 2.0 Vectors scores | |||
Detail
| In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change rfcomm_sk_state_change attempts to use sock_lock so it must never be called with it locked but rfcomm_sock_ioctl always attempt to lock it causing the following trace: ====================================================== WARNING: possible circular locking dependency detected 6.8.0-syzkaller-08951-gfe46a7dd189e #0 Not tainted ------------------------------------------------------ syz-executor386/5093 is trying to acquire lock: ffff88807c396258 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1671 [inline] ffff88807c396258 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: rfcomm_sk_state_change+0x5b/0x310 net/bluetooth/rfcomm/sock.c:73 but task is already holding lock: ffff88807badfd28 (&d->lock){+.+.}-{3:3}, at: __rfcomm_dlc_close+0x226/0x6a0 net/bluetooth/rfcomm/core.c:491 |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50044 |
CWE : Common Weakness Enumeration
| % | Id | Name |
|---|---|---|
| 100 % | CWE-667 | Insufficient Locking |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
| Date | Informations |
|---|---|
| 2025-06-26 02:36:32 |
|
| 2025-06-25 12:34:57 |
|
| 2025-06-24 02:41:11 |
|
| 2025-05-27 02:46:20 |
|
| 2025-03-29 03:42:22 |
|
| 2025-03-28 13:46:12 |
|
| 2025-03-28 03:20:07 |
|
| 2025-03-19 03:15:24 |
|
| 2025-03-18 03:28:21 |
|
| 2025-03-14 03:15:35 |
|
| 2025-03-06 14:12:09 |
|
| 2025-02-22 03:25:42 |
|
| 2025-01-08 03:06:36 |
|
| 2025-01-07 03:06:09 |
|
| 2024-12-25 03:04:47 |
|
| 2024-12-12 03:07:43 |
|
| 2024-11-23 03:04:34 |
|
| 2024-11-22 03:02:42 |
|
| 2024-11-20 03:00:59 |
|
| 2024-11-13 21:21:29 |
|
| 2024-11-09 00:28:08 |
|
| 2024-11-08 21:27:54 |
|
| 2024-10-26 02:58:06 |
|
| 2024-10-26 00:27:31 |
|
| 2024-10-25 03:00:33 |
|
| 2024-10-25 00:27:34 |
|
| 2024-10-23 21:27:32 |
|
| 2024-10-22 00:27:27 |
|
