LiveActive security incident?Get immediate response
CVE Record

CVE-2024-38662: bpf: Allow delete from sockmap/sockhash only if update is allowed

In the Linux kernel, the following vulnerability has been resolved: bpf: Allow delete from sockmap/sockhash only if update is allowed We have seen an influx of syzkaller reports where a BPF program attached to a tracepoint triggers a locking rule violation by performing a map_delete on a sockmap/sockhash. We don't intend to support this artificial use scenario. Extend the existing verifier allowed-program-type check for updating sockmap/sockhash to also cover deleting from a map. From now on only BPF programs which were previously allowed to update sockmap/sockhash can delete from these map types.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel eBPF issue where certain BPF programs could delete entries from sockmap or sockhash maps even though they were not allowed to update those maps. Reported syzkaller cases triggered a kernel locking rule violation. The public sources do not provide a CVSS score or evidence of real-world exploitation.

Executive priority

Treat as a kernel maintenance item with moderate priority unless your environment allows broad BPF use or includes exposed products named by vendor advisories. There is no source-supported active exploitation, but kernel issues can carry operational risk and should be remediated through normal patch governance.

Technical view

The fix extends the verifier’s existing allowed-program-type check for sockmap/sockhash updates to map deletion. The source describes tracepoint-attached BPF programs using map_delete on sockmap/sockhash and triggering locking violations. Linux stable commits are referenced, but the bundle does not provide exploitability details, impact severity, or distribution-specific package mappings.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel builds where BPF programs can be loaded and attached to tracepoints. Practical exposure depends on kernel version, distribution backports, and local BPF permissions. Siemens advisories indicate downstream product review, but the provided bundle does not state affected Siemens product details.

Exploitation context

CISA KEV status is false, and the provided sources do not cite active exploitation. The issue was observed through syzkaller reports, which suggests automated kernel testing rather than confirmed attacker use. No public exploit status is supported by the bundle.

Researcher notes

Focus analysis on verifier policy for sockmap and sockhash delete operations. The key behavioral change is parity between update and delete permission checks. Evidence is incomplete on attacker prerequisites and impact, so avoid assuming privilege escalation, denial of service, or product-specific exposure without vendor confirmation.

Mitigation direction

  • Apply Linux vendor kernel updates that include the referenced stable fixes.
  • Check distribution advisories for backported package versions.
  • Review Siemens advisories if operating Siemens products listed there.
  • Restrict BPF program loading according to vendor and platform guidance.
  • Track the CVE record for severity or affected-version updates.

Validation and detection

  • Identify running kernel versions across Linux assets.
  • Map kernels to vendor advisories or fixed stable commits.
  • Check whether BPF loading is enabled or restricted locally.
  • Prioritize systems allowing non-standard or broad BPF use.
  • Confirm Siemens advisory applicability for relevant products.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-38662 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
3ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxdd54b48db0c822ae7b520bc80751f0a0a173ef75, d1e73fb19a4c872d7a399ad3c66e8ca30e0875ec, a44770fed86515eedb5a7c00b787f847ebb134a5, 668b3074aa14829e2ac2759799537a93b60fef86, ff91059932401894e6c86341915615c5eb0eca48, ff91059932401894e6c86341915615c5eb0eca48, f7990498b05ac41f7d6a190dc0418ef1d21bf058, 6af057ccdd8e7619960aca1f0428339f213b31cdunaffected
LinuxLinux6.9, 0, 5.10.219, 5.15.161, 6.1.93, 6.6.33, 6.9.4, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.