In the Linux kernel, the following vulnerability has been resolved:
stackdepot: fix stack_depot_save_flags() in NMI context
Per documentation, stack_depot_save_flags() was meant to be usable from
NMI context if STACK_DEPOT_FLAG_CAN_ALLOC is unset. However, it still
would try to take the pool_lock in an attempt to save a stack trace in the
current pool (if space is available).
This could result in deadlock if an NMI is handled while pool_lock is
already held. To avoid deadlock, only try to take the lock in NMI context
and give up if unsuccessful.
The documentation is fixed to clearly convey this.
Metrics
Affected Vendors & Products
References
History
Thu, 13 Feb 2025 01:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | CWE-833 | |
Metrics |
threat_severity
|
threat_severity
|
Tue, 14 Jan 2025 08:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
cvssV3_1
|
Sat, 11 Jan 2025 12:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | In the Linux kernel, the following vulnerability has been resolved: stackdepot: fix stack_depot_save_flags() in NMI context Per documentation, stack_depot_save_flags() was meant to be usable from NMI context if STACK_DEPOT_FLAG_CAN_ALLOC is unset. However, it still would try to take the pool_lock in an attempt to save a stack trace in the current pool (if space is available). This could result in deadlock if an NMI is handled while pool_lock is already held. To avoid deadlock, only try to take the lock in NMI context and give up if unsuccessful. The documentation is fixed to clearly convey this. | |
Title | stackdepot: fix stack_depot_save_flags() in NMI context | |
References |
|

Status: PUBLISHED
Assigner: Linux
Published:
Updated: 2025-01-20T06:19:13.331Z
Reserved: 2025-01-09T09:51:32.384Z
Link: CVE-2024-48876

No data.

Status : Received
Published: 2025-01-11T13:15:23.263
Modified: 2025-01-11T13:15:23.263
Link: CVE-2024-48876
