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-2025-38502bpf: Fix oob access in cgroup local storage

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix oob access in cgroup local storage Lonial reported that an out-of-bounds access in cgroup local storage can be crafted via tail calls. Given two programs each utilizing a cgroup local storage with a different value size, and one program doing a tail call into the other. The verifier will validate each of the indivial programs just fine. However, in the runtime context the bpf_cg_run_ctx holds an bpf_prog_array_item which contains the BPF program as well as any cgroup local storage flavor the program uses. Helpers such as bpf_get_local_storage() pick this up from the runtime context: ctx = container_of(current->bpf_ctx, struct bpf_cg_run_ctx, run_ctx); storage = ctx->prog_item->cgroup_storage[stype]; if (stype == BPF_CGROUP_STORAGE_SHARED) ptr = &READ_ONCE(storage->buf)->data[0]; else ptr = this_cpu_ptr(storage->percpu_buf); For the second program which was called from the originally attached one, this means bpf_get_local_storage() will pick up the former program's map, not its own. With mismatching sizes, this can result in an unintended out-of-bounds access. To fix this issue, we need to extend bpf_map_owner with an array of storage_cookie[] to match on i) the exact maps from the original program if the second program was using bpf_get_local_storage(), or ii) allow the tail call combination if the second program was not using any of the cgroup local storage maps.

Timeline

  1. ID reserved

    By Linux

  2. · 4 months later

    Published

  3. · 14 months 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-2025-38502, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 7d9c3427894fe70d1347b4820476bf37736d2ff0 – < c1c74584b9b4043c52e41fec415226e582d266a3
    • affected 7d9c3427894fe70d1347b4820476bf37736d2ff0 – < 66da7cee78590259b400e51a70622ccd41da7bb2
    • affected 7d9c3427894fe70d1347b4820476bf37736d2ff0 – < 7acfa07c585e3d7a64654d38f0a5c762877d0b9b
    • affected 7d9c3427894fe70d1347b4820476bf37736d2ff0 – < 41688d1fc5d163a6c2c0e95c0419e2cb31a44648
    • affected 7d9c3427894fe70d1347b4820476bf37736d2ff0 – < 19341d5c59e8c7e8528e40f8663e99d67810473c
    • affected 7d9c3427894fe70d1347b4820476bf37736d2ff0 – < abad3d0bad72a52137e0c350c59542d75ae4f513
  • Linux · Linux

    • affected 5.9
    • unaffected < 5.9
    • unaffected 5.15.192 – ≤ 5.15.*
    • unaffected 6.1.151 – ≤ 6.1.*
    • unaffected 6.6.105 – ≤ 6.6.*
    • unaffected 6.12.46 – ≤ 6.12.*
    • unaffected 6.16.1 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .