stackdepot: fix stack_depot_save_flags() in NMI context
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's stack_depot_save_flags() can try to acquire pool_lock while handling a non-maskable interrupt (NMI), even when allocation is disabled. If the lock is already held, the kernel can deadlock. The input does not describe an attacker access path or any authentication or user-interaction requirements.
Anyone running the Linux kernel should check whether their version includes the stackdepot fix; affected versions are not specified.