Executive Summary

Informations
Name CVE-2024-43862 First vendor Publication 2024-08-21
Vendor Cve Last vendor Modification 2024-09-03

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:H
Overall CVSS Score 5.5
Base Score 5.5 Environmental Score 5.5
impact SubScore 3.6 Temporal Score 5.5
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 High
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:

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.

Original Source

Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43862

CWE : Common Weakness Enumeration

% Id Name
100 % CWE-667 Insufficient Locking

CPE : Common Platform Enumeration

TypeDescriptionCount
Application 8
Os 3625

Sources (Detail)

https://git.kernel.org/stable/c/c4d6a347ba7babdf9d90a0eb24048c266cae0532
https://git.kernel.org/stable/c/f223d2b4acb7a45a6e0581cb380e1af1a6dc7ab9
Source Url

Alert History

If you want to see full details history, please login or register.
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
Date Informations
2024-11-23 03:02:45
  • Multiple Updates
2024-11-22 03:00:56
  • Multiple Updates
2024-11-20 02:59:16
  • Multiple Updates
2024-11-14 02:59:35
  • Multiple Updates
2024-11-09 02:59:35
  • Multiple Updates
2024-10-26 02:56:58
  • Multiple Updates
2024-10-25 02:58:51
  • Multiple Updates
2024-10-23 02:58:03
  • Multiple Updates
2024-10-03 02:53:19
  • Multiple Updates
2024-10-02 02:51:43
  • Multiple Updates
2024-09-15 02:49:23
  • Multiple Updates
2024-09-11 21:27:50
  • Multiple Updates
2024-09-06 21:28:11
  • Multiple Updates
2024-09-06 00:27:52
  • Multiple Updates
2024-09-03 21:27:45
  • Multiple Updates
2024-09-03 17:27:41
  • Multiple Updates
2024-08-22 02:48:16
  • Multiple Updates
2024-08-22 02:48:01
  • Multiple Updates
2024-08-21 17:27:26
  • Multiple Updates
2024-08-21 09:27:29
  • First insertion