Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2024-46797 | First vendor Publication | 2024-09-18 |
Vendor | Cve | Last vendor Modification | 2024-09-29 |
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: powerpc/qspinlock: Fix deadlock in MCS queue If an interrupt occurs in queued_spin_lock_slowpath() after we increment qnodesp->count and before node->lock is initialized, another CPU might see stale lock values in get_tail_qnode(). If the stale lock value happens to match the lock on that CPU, then we write to the "next" pointer of the wrong qnode. This causes a deadlock as the former CPU, once it becomes the head of the MCS queue, will spin indefinitely until it's "next" pointer is set by its successor in the queue. Running stress-ng on a 16 core (16EC/16VP) shared LPAR, results in occasional lockups similar to the following: $ stress-ng --all 128 --vm-bytes 80% --aggressive \ watchdog: CPU 15 Hard LOCKUP The following code flow illustrates how the deadlock occurs. For the sake of brevity, assume that both locks (A and B) are contended and we call the queued_spin_lock_slowpath() function. CPU0 CPU1 |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-46797 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-667 | Insufficient Locking |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2025-03-29 03:40:40 |
|
2025-03-28 13:45:04 |
|
2025-03-28 03:18:45 |
|
2025-03-19 03:14:05 |
|
2025-03-18 03:27:01 |
|
2025-03-14 03:14:18 |
|
2025-03-06 14:10:50 |
|
2025-02-22 03:24:24 |
|
2025-01-08 03:05:25 |
|
2025-01-07 03:04:58 |
|
2024-12-25 03:03:35 |
|
2024-12-12 03:06:32 |
|
2024-11-23 03:03:30 |
|
2024-11-22 03:01:39 |
|
2024-11-20 02:59:58 |
|
2024-11-14 03:00:17 |
|
2024-11-09 03:00:17 |
|
2024-10-26 02:57:40 |
|
2024-10-25 02:59:32 |
|
2024-10-23 02:58:44 |
|
2024-10-02 17:27:39 |
|
2024-10-02 00:27:47 |
|
2024-09-29 21:27:28 |
|
2024-09-21 05:27:30 |
|
2024-09-20 17:27:27 |
|
2024-09-18 13:27:29 |
|