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

Metrics

No CVSS v4.0

Attack Vector Local

Attack Complexity Low

Privileges Required Low

Scope Unchanged

Confidentiality Impact None

Integrity Impact None

Availability Impact Low

User Interaction None

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

Exploitation none

Automatable no

Technical Impact partial

Affected Vendors & Products

Vendors Products
Linux
  • Linux Kernel

Configuration 1 [-]

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc2:*:*:*:*:*:*

No data.

References
Link Providers
https://git.kernel.org/stable/c/08d1914293dae38350b8088980e59fbc699a72fe cve-icon cve-icon
https://git.kernel.org/stable/c/38b2d5a57d125e1c17661b8308c0240c4a43b534 cve-icon cve-icon
https://git.kernel.org/stable/c/496b2ab0fd10f205e08909a125485fdc98843dbe cve-icon cve-icon
https://git.kernel.org/stable/c/4cb9807c9b53bf1e5560420d26f319f528b50268 cve-icon cve-icon
https://git.kernel.org/stable/c/869c6ee62ab8f01bf2419e45326642be5c9b670a cve-icon cve-icon
https://git.kernel.org/stable/c/b77b3fb12fd483cae7c28648903b1d8a6b275f01 cve-icon cve-icon
https://git.kernel.org/stable/c/ced98072d3511b232ae1d3347945f35f30c0e303 cve-icon cve-icon
https://git.kernel.org/stable/c/ef44274dae9b0a90d1a97ce8b242a3b8243a7745 cve-icon cve-icon
https://lore.kernel.org/linux-cve-announce/2024102133-CVE-2024-50044-2ee1@gregkh/T cve-icon
https://nvd.nist.gov/vuln/detail/CVE-2024-50044 cve-icon
https://www.cve.org/CVERecord?id=CVE-2024-50044 cve-icon
History

Fri, 22 Nov 2024 15:45:00 +0000

Type Values Removed Values Added
Metrics threat_severity

Moderate

 threat_severity

Low

Fri, 08 Nov 2024 16:15:00 +0000

Type Values Removed Values Added
References

Thu, 24 Oct 2024 20:00:00 +0000

Type Values Removed Values Added
First Time appeared Linux
Linux linux Kernel
Weaknesses CWE-667
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc2:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
Metrics cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

 cvssV3_1

{'score': 3.3, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L'}

Tue, 22 Oct 2024 14:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Tue, 22 Oct 2024 13:30:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

 cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate

Mon, 21 Oct 2024 19:45:00 +0000

Type Values Removed Values Added
Description 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
Title Bluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change
References
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published: 2024-10-21T19:39:42.430Z

Updated: 2024-12-19T09:31:59.938Z

Reserved: 2024-10-21T12:17:06.071Z

Link: CVE-2024-50044

cve-icon Vulnrichment

Updated: 2024-10-22T13:24:26.102Z

cve-icon NVD

Status : Modified

Published: 2024-10-21T20:15:17.313

Modified: 2024-11-08T16:15:44.520

Link: CVE-2024-50044

cve-icon Redhat

Severity : Low

Publid Date: 2024-10-21T00:00:00Z

Links: CVE-2024-50044 - Bugzilla