Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-38662, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.7.

Affected products

  • Linux · Linux

    • affected dd54b48db0c822ae7b520bc80751f0a0a173ef75 – < 29467edc23818dc5a33042ffb4920b49b090e63d
    • affected d1e73fb19a4c872d7a399ad3c66e8ca30e0875ec – < 11e8ecc5b86037fec43d07b1c162e233e131b1d9
    • affected a44770fed86515eedb5a7c00b787f847ebb134a5 – < 6693b172f008846811f48a099f33effc26068e1e
    • affected 668b3074aa14829e2ac2759799537a93b60fef86 – < 000a65bf1dc04fb2b65e2abf116f0bc0fc2ee7b1
    • affected ff91059932401894e6c86341915615c5eb0eca48 – < b81e1c5a3c70398cf76631ede63a03616ed1ba3c
    • affected ff91059932401894e6c86341915615c5eb0eca48 – < 98e948fb60d41447fd8d2d0c3b8637fc6b6dc26d
    • affected f7990498b05ac41f7d6a190dc0418ef1d21bf058
    • affected 6af057ccdd8e7619960aca1f0428339f213b31cd
    • affected 5.10.215 – < 5.10.219
    • affected 5.15.154 – < 5.15.161
    • affected 6.1.85 – < 6.1.93
    • affected 6.6.26 – < 6.6.33
    • affected 5.4.274 – < 5.5
    • affected 6.8.5 – < 6.9
  • Linux · Linux

    • affected 6.9
    • unaffected < 6.9
    • unaffected 5.10.219 – ≤ 5.10.*
    • unaffected 5.15.161 – ≤ 5.15.*
    • unaffected 6.1.93 – ≤ 6.1.*
    • unaffected 6.6.33 – ≤ 6.6.*
    • unaffected 6.9.4 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-38662 badge
[![CVE-2024-38662](https://cveledger.app/badge/CVE-2024-38662.svg)](https://cveledger.app/cve/CVE-2024-38662)

Record last updated .