CVE-2024-56694: bpf: fix recursive lock when verdict program return SK_PASS
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.41% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 01f1b88acfd79103da0610b45471f6c88ea98d72, 221109ba2127eabd0aa64718543638b58b15df56, 386efa339e08563dd33e83bc951aea5d407fe578; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1.
- Severity is disputed: the assigning authority (CNA) scores it 7.5, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 01f1b88acfd79103da0610b45471f6c88ea98d72, 221109ba2127eabd0aa64718543638b58b15df56, 386efa339e08563dd33e83bc951aea5d407fe578; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Published
- Dec 28, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.4% · 36th percentile
- CWE
- CWE-667
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.5
- 2.0 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 772d5729b5ff0df0d37b32db600ce635b2172f80, 6.9affected
- c0809c128dad4c3413818384eb06a341633db973 and later · before 221109ba2127eabd0aa64718543638b58b15df56affected · git
- 5965bc7535fb87510b724e5465ccc1a1cf00916d and later · before 6694f7acd625ed854bf6342926e771d65dad7f69affected · git
- 39dc9e1442385d6e9be0b6491ee488dddd55ae27 and later · before 386efa339e08563dd33e83bc951aea5d407fe578affected · git
- b397a0ab8582c533ec0c6b732392f141fc364f87 and later · before da2bc8a0c8f3ac66fdf980fc59936f851a083561affected · git
- 6648e613226e18897231ab5e42ffc29e63fa3365 and later · before 01f1b88acfd79103da0610b45471f6c88ea98d72affected · git
- 6648e613226e18897231ab5e42ffc29e63fa3365 and later · before f84c5ef6ca23cc2f72f3b830d74f67944684bb05affected · git
- 6648e613226e18897231ab5e42ffc29e63fa3365 and later · before 8ca2a1eeadf09862190b2810697702d803ceef2daffected · git
- 5.10.223 and later · before 5.10.233affected · semver
- 5.15.159 and later · before 5.15.174affected · semver
Affected versions · NVD (6)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.10.223 and later · before 5.11
- linux linux kernel5.15.159 and later · before 5.15.174
- linux linux kernel6.1.91 and later · before 6.1.120
- linux linux kernel6.6.31 and later · before 6.6.64
- linux linux kernel6.8.10 and later · before 6.11.11
- linux linux kernel6.12 and later · before 6.12.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.123-1 | 6.1.123-1 |
| Debian:13 | linux | before 6.12.3-1 | 6.12.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-56691Dec 28, 2024 · mfd: intel_soc_pmic_bxtwc: Use IRQ domain for USB Type-C device22Monitor
- ← EarlierCVE-2024-56693Dec 28, 2024 · brd: defer automatic disk creation until module initialization succeeds31Monitor
- Later →CVE-2024-56695Dec 28, 2024 · drm/amdkfd: Use dynamic allocation for CU occupancy array in 'kfd_get_cu_occupancy()'31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 01f1b88acfd79103da0610b45471f6c88ea98d72 | Vendor (CNA) |
| Linux Linux | 221109ba2127eabd0aa64718543638b58b15df56 | Vendor (CNA) |
| Linux Linux | 386efa339e08563dd33e83bc951aea5d407fe578 | Vendor (CNA) |
| Linux Linux | 5.10.233 | Vendor (CNA) |
| Linux Linux | 5.15.174 | Vendor (CNA) |
| Linux Linux | 6.1.120 | Vendor (CNA) |
| Linux Linux | 6.6.64 | Vendor (CNA) |
| Linux Linux | 6.9 | Vendor (CNA) |
| Linux Linux | 6694f7acd625ed854bf6342926e771d65dad7f69 | Vendor (CNA) |
| Linux Linux | 8ca2a1eeadf09862190b2810697702d803ceef2d | Vendor (CNA) |
| Linux Linux | da2bc8a0c8f3ac66fdf980fc59936f851a083561 | Vendor (CNA) |
| Linux Linux | f84c5ef6ca23cc2f72f3b830d74f67944684bb05 | Vendor (CNA) |
| azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 | 6.6.64.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 | 6.6.64.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.173.1-2 on CBL Mariner 2.0 | 5.15.176.3-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.173.1-2 on CBL-Mariner 2.0 | 5.15.176.3-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.176.3-1 on CBL Mariner 2.0 | 5.15.176.3-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.123-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-667 · Improper LockingCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/221109ba2127eabd0aa64718543638b58b15df56
- git.kernel.org/stable/c/386efa339e08563dd33e83bc951aea5d407fe578
- git.kernel.org/stable/c/6694f7acd625ed854bf6342926e771d65dad7f69
- git.kernel.org/stable/c/8ca2a1eeadf09862190b2810697702d803ceef2d
- git.kernel.org/stable/c/da2bc8a0c8f3ac66fdf980fc59936f851a083561
- git.kernel.org/stable/c/f84c5ef6ca23cc2f72f3b830d74f67944684bb05
- lists.debian.org/debian-lts-announce/2025/03/msg00001.html
- lists.debian.org/debian-lts-announce/2025/03/msg00002.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.