CVE-2024-58070: bpf: bpf_local_storage: Always use bpf_mem_alloc in PREEMPT_RT
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.14% (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 3392fa605d7c5708c5fbe02e4fbdac547c3b7352, 8eef6ac4d70eb1f0099fff93321d90ce8fa49ee1, b0027500000dfcb8ee952557d565064cea22c43e.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 3392fa605d7c5708c5fbe02e4fbdac547c3b7352, 8eef6ac4d70eb1f0099fff93321d90ce8fa49ee1, b0027500000dfcb8ee952557d565064cea22c43e 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: bpf_local_storage: Always use bpf_mem_alloc in PREEMPT_RT In PREEMPT_RT, kmalloc(GFP_ATOMIC) is still not safe in non preemptible context. bpf_mem_alloc must be used in PREEMPT_RT. This patch is to enforce bpf_mem_alloc in the bpf_local_storage when CONFIG_PREEMPT_RT is enabled. [ 35.118559] BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48 [ 35.118566] in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1832, name: test_progs [ 35.118569] preempt_count: 1, expected: 0 [ 35.118571] RCU nest depth: 1, expected: 1 [ 35.118577] INFO: lockdep is turned off. ... [ 35.118647] __might_resched+0x433/0x5b0 [ 35.118677] rt_spin_lock+0xc3/0x290 [ 35.118700] ___slab_alloc+0x72/0xc40 [ 35.118723] __kmalloc_noprof+0x13f/0x4e0 [ 35.118732] bpf_map_kzalloc+0xe5/0x220 [ 35.118740] bpf_selem_alloc+0x1d2/0x7b0 [ 35.118755] bpf_local_storage_update+0x2fa/0x8b0 [ 35.118784] bpf_sk_storage_get_tracing+0x15a/0x1d0 [ 35.118791] bpf_prog_9a118d86fca78ebb_trace_inet_sock_set_state+0x44/0x66 [ 35.118795] bpf_trace_run3+0x222/0x400 [ 35.118820] __bpf_trace_inet_sock_set_state+0x11/0x20 [ 35.118824] trace_inet_sock_set_state+0x112/0x130 [ 35.118830] inet_sk_state_store+0x41/0x90 [ 35.118836] tcp_set_state+0x3b3/0x640 There is no need to adjust the gfp_flags passing to the bpf_mem_cache_alloc_flags() which only honors the GFP_KERNEL. The verifier has ensured GFP_KERNEL is passed only in sleepable context. It has been an old issue since the first introduction of the bpf_local_storage ~5 years ago, so this patch targets the bpf-next. bpf_mem_alloc is needed to solve it, so the Fixes tag is set to the commit when bpf_mem_alloc was first used in the bpf_local_storage.
- Published
- Mar 6, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.1% · 4th 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.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.8
- 2.3 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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
- 6.4affected
- 08a7ce384e33e53e0732c500a8af67a73f8fceca and later · before 3392fa605d7c5708c5fbe02e4fbdac547c3b7352affected · git
- 08a7ce384e33e53e0732c500a8af67a73f8fceca and later · before b0027500000dfcb8ee952557d565064cea22c43eaffected · git
- 08a7ce384e33e53e0732c500a8af67a73f8fceca and later · before c1d398a3af7e59d7fef351c84fed7ebb575d1f1aaffected · git
- 08a7ce384e33e53e0732c500a8af67a73f8fceca and later · before 8eef6ac4d70eb1f0099fff93321d90ce8fa49ee1affected · git
- before 6.4not affected · semver
- 6.6.76 and later · up to and including 6.6.*not affected · semver
- 6.12.13 and later · up to and including 6.12.*not affected · semver
- 6.13.2 and later · up to and including 6.13.*not affected · semver
- 6.14 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.4 and later · before 6.6.76
- linux linux kernel6.7 and later · before 6.12.13
- linux linux kernel6.13 and later · before 6.13.2
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.13-1 | 6.12.13-1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7-RT_Update_1 | before 1-150700.1.3.1 | 1-150700.1.3.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 |
| SUSE:Real Time Module 15 SP7 | kernel-rt | before 6.4.0-150700.7.3.1 | 6.4.0-150700.7.3.1 |
| SUSE:Real Time Module 15 SP7 | kernel-rt_debug | before 6.4.0-150700.7.3.1 | 6.4.0-150700.7.3.1 |
| SUSE:Real Time Module 15 SP7 | kernel-source-rt | before 6.4.0-150700.7.3.1 | 6.4.0-150700.7.3.1 |
| SUSE:Real Time Module 15 SP7 | kernel-syms-rt | before 6.4.0-150700.7.3.1 | 6.4.0-150700.7.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-58067Mar 6, 2025 · clk: mmp: pxa1908-mpmu: Fix a NULL vs IS_ERR() check22Monitor
- ← EarlierCVE-2024-58069Mar 6, 2025 · rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read31Monitor
- Later →CVE-2024-58073Mar 6, 2025 · drm/msm/dpu: check dpu_plane_atomic_print_state() for valid sspp22Monitor
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 | 3392fa605d7c5708c5fbe02e4fbdac547c3b7352 | Vendor (CNA) |
| Linux Linux | 8eef6ac4d70eb1f0099fff93321d90ce8fa49ee1 | Vendor (CNA) |
| Linux Linux | b0027500000dfcb8ee952557d565064cea22c43e | Vendor (CNA) |
| Linux Linux | c1d398a3af7e59d7fef351c84fed7ebb575d1f1a | Vendor (CNA) |
| debian:linux | 6.12.13-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-livepatch-SLE15-SP7-RT_Update_1 | 1-150700.1.3.1 · SUSE:Linux Enterprise Live Patching 15 SP7 | Package registry (OSV) |
| suse:kernel-rt | 6.4.0-150700.7.3.1 · SUSE:Real Time Module 15 SP7 | Package registry (OSV) |
| suse:kernel-rt_debug | 6.4.0-150700.7.3.1 · SUSE:Real Time Module 15 SP7 | 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-150700.7.3.1 · SUSE:Real Time Module 15 SP7 | Package registry (OSV) |
| suse:kernel-syms-rt | 6.4.0-150700.7.3.1 · SUSE:Real Time Module 15 SP7 | 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.