CVE-2024-43862

  1. OpenCVE
  2. Vulnerabilities (CVE)
  3. CVE-2024-43862
In the Linux kernel, the following vulnerability has been resolved: net: wan: fsl_qmc_hdlc: Convert carrier_lock spinlock to a mutex The carrier_lock spinlock protects the carrier detection. While it is held, framer_get_status() is called which in turn takes a mutex. This is not correct and can lead to a deadlock. A run with PROVE_LOCKING enabled detected the issue: [ BUG: Invalid wait context ] ... c204ddbc (&framer->mutex){+.+.}-{3:3}, at: framer_get_status+0x40/0x78 other info that might help us debug this: context-{4:4} 2 locks held by ifconfig/146: #0: c0926a38 (rtnl_mutex){+.+.}-{3:3}, at: devinet_ioctl+0x12c/0x664 #1: c2006a40 (&qmc_hdlc->carrier_lock){....}-{2:2}, at: qmc_hdlc_framer_set_carrier+0x30/0x98 Avoid the spinlock usage and convert carrier_lock to a mutex.

5.5 /10

CVSS v3 : MEDIUM

V3 Legend

Vector :

Exploitability : 1.8 / Impact : 3.6

Attack Vector LOCAL

Attack Complexity LOW

Privileges Required LOW

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact NONE

Availability Impact HIGH

Scope UNCHANGED

References
Link Resource
https://git.kernel.org/stable/c/c4d6a347ba7babdf9d90a0eb24048c266cae0532 Patch
https://git.kernel.org/stable/c/f223d2b4acb7a45a6e0581cb380e1af1a6dc7ab9 Patch
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.11:rc1:*:*:*:*:*:*
History

03 Sep 2024, 13:44

Type Values Removed Values Added
References () https://git.kernel.org/stable/c/c4d6a347ba7babdf9d90a0eb24048c266cae0532 - () https://git.kernel.org/stable/c/c4d6a347ba7babdf9d90a0eb24048c266cae0532 - Patch
References () https://git.kernel.org/stable/c/f223d2b4acb7a45a6e0581cb380e1af1a6dc7ab9 - () https://git.kernel.org/stable/c/f223d2b4acb7a45a6e0581cb380e1af1a6dc7ab9 - Patch
Summary
  • (es) En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: net: wan: fsl_qmc_hdlc: convierte el spinlock de Carrier_lock en un mutex El spinlock de Carrier_lock protege la detección del operador. Mientras se mantiene, se llama a framer_get_status(), que a su vez toma un mutex. Esto no es correcto y puede llevar a un punto muerto. Una ejecución con PROVE_LOCKING habilitado detectó el problema: [ERROR: Contexto de espera no válido] ... c204ddbc (&framer->mutex){+.+.}-{3:3}, en: framer_get_status+0x40/0x78 otra información que podría ayúdenos a depurar esto: contexto-{4:4} 2 bloqueos retenidos por ifconfig/146: #0: c0926a38 (rtnl_mutex){+.+.}-{3:3}, en: devinet_ioctl+0x12c/0x664 #1: c2006a40 (&qmc_hdlc->carrier_lock){....}-{2:2}, en: qmc_hdlc_framer_set_carrier+0x30/0x98 Evite el uso de spinlock y convierta carrier_lock en un mutex.
CWE CWE-667
CVSS v2 : unknown
v3 : unknown 		v2 : unknown
v3 : 5.5
First Time Linux linux Kernel
Linux
CPE cpe:2.3:o:linux:linux_kernel:6.11:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

21 Aug 2024, 00:15

Type Values Removed Values Added
New CVE
Information

Published : 2024-08-21 00:15

Updated : 2024-09-03 13:44

NVD link : CVE-2024-43862

Mitre link : CVE-2024-43862

CVE.ORG link : CVE-2024-43862

JSON object : View

Products Affected

linux

  • linux_kernel
CWE
CWE-667

Improper Locking