stackdepot: fix stack_depot_save_flags() in NMI context
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 031e04bdc834cda3b054ef6b698503b2b97e8186 and Kernel 9bfeeeff2c92b9dd261198b601b45bde4c529841.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.8, >=4434a56ec20925333d6cf4d4093641d063abd35b <031e04bdc834cda3b054ef6b698503b2b97e8186, >=4434a56ec20925333d6cf4d4093641d063abd35b <9bfeeeff2c92b9dd261198b601b45bde4c529841 | 031e04bdc834cda3b054ef6b698503b2b97e8186, 9bfeeeff2c92b9dd261198b601b45bde4c529841 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket