Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-35895: bpf, sockmap: Prevent lock inversion deadlock in map delete elem

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 668b3074aa14829e2ac2759799537a93b60fef86, 6af057ccdd8e7619960aca1f0428339f213b31cd, a44770fed86515eedb5a7c00b787f847ebb134a5.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 668b3074aa14829e2ac2759799537a93b60fef86, 6af057ccdd8e7619960aca1f0428339f213b31cd, a44770fed86515eedb5a7c00b787f847ebb134a5 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, sockmap: Prevent lock inversion deadlock in map delete elem syzkaller started using corpuses where a BPF tracing program deletes elements from a sockmap/sockhash map. Because BPF tracing programs can be invoked from any interrupt context, locks taken during a map_delete_elem operation must be hardirq-safe. Otherwise a deadlock due to lock inversion is possible, as reported by lockdep: CPU0 CPU1 ---- ---- lock(&htab->buckets[i].lock); local_irq_disable(); lock(&host->lock); lock(&htab->buckets[i].lock); <Interrupt> lock(&host->lock); Locks in sockmap are hardirq-unsafe by design. We expects elements to be deleted from sockmap/sockhash only in task (normal) context with interrupts enabled, or in softirq context. Detect when map_delete_elem operation is invoked from a context which is _not_ hardirq-unsafe, that is interrupts are disabled, and bail out with an error. Note that map updates are not affected by this issue. BPF verifier does not allow updating sockmap/sockhash from a BPF tracing program today.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 19, 2024
Updated
Oct 15, 2026
EPSS
0.1% · 7th percentile

Report tools

JSON

Action score

22

Monitor

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.

Follow CVE-2024-35895

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux10.0
  • linux linux kernel5.5 and later · before 5.10.215
  • linux linux kernel5.11 and later · before 5.15.154
  • linux linux kernel5.16 and later · before 6.1.85
  • linux linux kernel4.20 and later · before 5.4.274
  • linux linux kernel6.7 and later · before 6.8.5
  • linux linux kernel6.2 and later · before 6.6.26
  • linux linux kernel6.9

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

    • 4.20affected
    • 604326b41a6fb9b4a78b6179335decee0365cd8c and later · before f7990498b05ac41f7d6a190dc0418ef1d21bf058affected · git
    • 604326b41a6fb9b4a78b6179335decee0365cd8c and later · before dd54b48db0c822ae7b520bc80751f0a0a173ef75affected · git
    • 604326b41a6fb9b4a78b6179335decee0365cd8c and later · before d1e73fb19a4c872d7a399ad3c66e8ca30e0875ecaffected · git
    • 604326b41a6fb9b4a78b6179335decee0365cd8c and later · before a44770fed86515eedb5a7c00b787f847ebb134a5affected · git
    • 604326b41a6fb9b4a78b6179335decee0365cd8c and later · before 668b3074aa14829e2ac2759799537a93b60fef86affected · git
    • 604326b41a6fb9b4a78b6179335decee0365cd8c and later · before 6af057ccdd8e7619960aca1f0428339f213b31cdaffected · git
    • 604326b41a6fb9b4a78b6179335decee0365cd8c and later · before ff91059932401894e6c86341915615c5eb0eca48affected · git
    • before 4.20not affected · semver
    • 5.4.274 and later · up to and including 5.4.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9bpftoolbefore 7.3.0-427.37.1.el9_47.3.0-427.37.1.el9_4
AlmaLinux:9kernelbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64kbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-corebefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-debugbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-develbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-corebefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-cross-headersbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-debugbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-debug-corebefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-debug-develbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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 KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-35888May 19, 2024 · erspan: make sure erspan_base_hdr is present in skb->head
    29Monitor
  • ← EarlierCVE-2024-35893May 19, 2024 · net/sched: act_skbmod: prevent kernel-infoleak
    22Monitor
  • Later →CVE-2024-35896May 19, 2024 · netfilter: validate user input for expected length
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux668b3074aa14829e2ac2759799537a93b60fef86Vendor (CNA)
Linux Linux6af057ccdd8e7619960aca1f0428339f213b31cdVendor (CNA)
Linux Linuxa44770fed86515eedb5a7c00b787f847ebb134a5Vendor (CNA)
Linux Linuxd1e73fb19a4c872d7a399ad3c66e8ca30e0875ecVendor (CNA)
Linux Linuxdd54b48db0c822ae7b520bc80751f0a0a173ef75Vendor (CNA)
Linux Linuxf7990498b05ac41f7d6a190dc0418ef1d21bf058Vendor (CNA)
Linux Linuxff91059932401894e6c86341915615c5eb0eca48Vendor (CNA)
almalinux:bpftool7.3.0-427.37.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-427.37.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-427.37.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-427.37.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-427.37.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-427.37.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-427.37.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-427.37.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-427.37.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-427.37.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-427.37.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-427.37.1.el9_4 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.85-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.0.0-284.82.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-284.82.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-284.82.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-284.82.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-284.82.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-284.82.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-284.82.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-284.82.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-284.82.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-284.82.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)

+2

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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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 Locking

CVSS 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)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records