CVE-2024-58088: bpf: Fix deadlock when freeing cgroup storage
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.18% (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 6ecb9fa14eec5f15d97c84c36896871335f6ddfb, c78f4afbd962f43a3989f45f3ca04300252b19b5, fac674d2bd68f3479f27328626b42d1eebd11fef; azl3 kernel 6.6.78.1-3 on Azure Linux 3.0 6.6.82.1-1; azl3 kernel 6.6.82.1-1 on Azure Linux 3.0 6.6.82.1-1.
Low priority for now. Upgrade to Linux Linux 6ecb9fa14eec5f15d97c84c36896871335f6ddfb, c78f4afbd962f43a3989f45f3ca04300252b19b5, fac674d2bd68f3479f27328626b42d1eebd11fef; azl3 kernel 6.6.78.1-3 on Azure Linux 3.0 6.6.82.1-1; azl3 kernel 6.6.82.1-1 on Azure Linux 3.0 6.6.82.1-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 deadlock when freeing cgroup storage The following commit bc235cdb423a ("bpf: Prevent deadlock from recursive bpf_task_storage_[get|delete]") first introduced deadlock prevention for fentry/fexit programs attaching on bpf_task_storage helpers. That commit also employed the logic in map free path in its v6 version. Later bpf_cgrp_storage was first introduced in c4bcfb38a95e ("bpf: Implement cgroup storage available to non-cgroup-attached bpf progs") which faces the same issue as bpf_task_storage, instead of its busy counter, NULL was passed to bpf_local_storage_map_free() which opened a window to cause deadlock: <TASK> (acquiring local_storage->lock) _raw_spin_lock_irqsave+0x3d/0x50 bpf_local_storage_update+0xd1/0x460 bpf_cgrp_storage_get+0x109/0x130 bpf_prog_a4d4a370ba857314_cgrp_ptr+0x139/0x170 ? __bpf_prog_enter_recur+0x16/0x80 bpf_trampoline_6442485186+0x43/0xa4 cgroup_storage_ptr+0x9/0x20 (holding local_storage->lock) bpf_selem_unlink_storage_nolock.constprop.0+0x135/0x160 bpf_selem_unlink_storage+0x6f/0x110 bpf_local_storage_map_free+0xa2/0x110 bpf_map_free_deferred+0x5b/0x90 process_one_work+0x17c/0x390 worker_thread+0x251/0x360 kthread+0xd2/0x100 ret_from_fork+0x34/0x50 ret_from_fork_asm+0x1a/0x30 </TASK> Progs: - A: SEC("fentry/cgroup_storage_ptr") - cgid (BPF_MAP_TYPE_HASH) Record the id of the cgroup the current task belonging to in this hash map, using the address of the cgroup as the map key. - cgrpa (BPF_MAP_TYPE_CGRP_STORAGE) If current task is a kworker, lookup the above hash map using function parameter @owner as the key to get its corresponding cgroup id which is then used to get a trusted pointer to the cgroup through bpf_cgroup_from_id(). This trusted pointer can then be passed to bpf_cgrp_storage_get() to finally trigger the deadlock issue. - B: SEC("tp_btf/sys_enter") - cgrpb (BPF_MAP_TYPE_CGRP_STORAGE) The only purpose of this prog is to fill Prog A's hash map by calling bpf_cgrp_storage_get() for as many userspace tasks as possible. Steps to reproduce: - Run A; - while (true) { Run B; Destroy B; } Fix this issue by passing its busy counter to the free procedure so it can be properly incremented before storage/smap locking.
- Published
- Mar 12, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 7th 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.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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
- 6.2affected
- c4bcfb38a95edb1021a53f2d0356a78120ecfbe4 and later · before 6ecb9fa14eec5f15d97c84c36896871335f6ddfbaffected · git
- c4bcfb38a95edb1021a53f2d0356a78120ecfbe4 and later · before fac674d2bd68f3479f27328626b42d1eebd11fefaffected · git
- c4bcfb38a95edb1021a53f2d0356a78120ecfbe4 and later · before fcec95b4ab3e7bc6b2f36e5d59f7e24104ea87f7affected · git
- c4bcfb38a95edb1021a53f2d0356a78120ecfbe4 and later · before c78f4afbd962f43a3989f45f3ca04300252b19b5affected · git
- before 6.2not affected · semver
- 6.6.80 and later · up to and including 6.6.*not affected · semver
- 6.12.17 and later · up to and including 6.12.*not affected · semver
- 6.13.5 and later · up to and including 6.13.*not affected · semver
- 6.14 and laternot affected · original_commit_for_fix
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.2 and later · before 6.6.80
- linux linux kernel6.7 and later · before 6.12.17
- linux linux kernel6.13 and later · before 6.13.5
- linux linux kernel6.14
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.17-1 | 6.12.17-1 |
| SUSE:Linux Micro 6.0 | kernel-default | before 6.4.0-29.1 | 6.4.0-29.1 |
| SUSE:Linux Micro 6.0 | kernel-default-base | before 6.4.0-29.1.21.7 | 6.4.0-29.1.21.7 |
| SUSE:Linux Micro 6.0 | kernel-kvmsmall | before 6.4.0-29.1 | 6.4.0-29.1 |
| SUSE:Linux Micro 6.0 | kernel-livepatch-MICRO-6-0_Update_7 | before 1-1.2 | 1-1.2 |
| SUSE:Linux Micro 6.0 | kernel-livepatch-MICRO-6-0-RT_Update_8 | before 1-1.2 | 1-1.2 |
| SUSE:Linux Micro 6.0 | kernel-rt | before 6.4.0-31.1 | 6.4.0-31.1 |
| SUSE:Linux Micro 6.0 | kernel-source | before 6.4.0-29.1 | 6.4.0-29.1 |
| SUSE:Linux Micro 6.0 | kernel-source-rt | before 6.4.0-31.1 | 6.4.0-31.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-2025-21839Mar 7, 2025 · KVM: x86: Load DR6 with guest value only before entering .vcpu_run() loop22Monitor
- ← EarlierCVE-2024-58087Mar 12, 2025 · ksmbd: fix racy issue from session lookup and expire32Monitor
- Later →CVE-2024-58089Mar 12, 2025 · btrfs: fix double accounting race when btrfs_run_delalloc_range() failed22Monitor
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 | 6ecb9fa14eec5f15d97c84c36896871335f6ddfb | Vendor (CNA) |
| Linux Linux | c78f4afbd962f43a3989f45f3ca04300252b19b5 | Vendor (CNA) |
| Linux Linux | fac674d2bd68f3479f27328626b42d1eebd11fef | Vendor (CNA) |
| Linux Linux | fcec95b4ab3e7bc6b2f36e5d59f7e24104ea87f7 | Vendor (CNA) |
| azl3 kernel 6.6.78.1-3 on Azure Linux 3.0 | 6.6.82.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.82.1-1 on Azure Linux 3.0 | 6.6.82.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.12.17-1 · Debian:13 | Package registry (OSV) |
| suse:kernel-default | 6.4.0-29.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-default-base | 6.4.0-29.1.21.7 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-kvmsmall | 6.4.0-29.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0_Update_7 | 1-1.2 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0-RT_Update_8 | 1-1.2 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-rt | 6.4.0-31.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-source | 6.4.0-29.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-source-rt | 6.4.0-31.1 · SUSE:Linux Micro 6.0 | 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 (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.