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-68742bpf: Fix invalid prog->stats access when update_effective_progs fails

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix invalid prog->stats access when update_effective_progs fails Syzkaller triggers an invalid memory access issue following fault injection in update_effective_progs. The issue can be described as follows: __cgroup_bpf_detach update_effective_progs compute_effective_progs bpf_prog_array_alloc <-- fault inject purge_effective_progs /* change to dummy_bpf_prog */ array->items[index] = &dummy_bpf_prog.prog ---softirq start--- __do_softirq ... __cgroup_bpf_run_filter_skb __bpf_prog_run_save_cb bpf_prog_run stats = this_cpu_ptr(prog->stats) /* invalid memory access */ flags = u64_stats_update_begin_irqsave(&stats->syncp) ---softirq end--- static_branch_dec(&cgroup_bpf_enabled_key[atype]) The reason is that fault injection caused update_effective_progs to fail and then changed the original prog into dummy_bpf_prog.prog in purge_effective_progs. Then a softirq came, and accessing the members of dummy_bpf_prog.prog in the softirq triggers invalid mem access. To fix it, skip updating stats when stats is NULL.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 11 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (19 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 492ecee892c2a4ba6a14903d5d586ff750b7e805 – < 93d1964773ff513c9bd530f7686d3e48b786fa6b
    • affected 492ecee892c2a4ba6a14903d5d586ff750b7e805 – < bf2c990b012100610c0f1ec5c4ea434da2d080c2
    • affected 492ecee892c2a4ba6a14903d5d586ff750b7e805 – < 539137e3038ce6f953efd72110110f03c14c7d97
    • affected 492ecee892c2a4ba6a14903d5d586ff750b7e805 – < 56905bb70c8b88421709bb4e32fcba617aa37d41
    • affected 492ecee892c2a4ba6a14903d5d586ff750b7e805 – < 2579c356ccd35d06238b176e4b460978186d804b
    • affected 492ecee892c2a4ba6a14903d5d586ff750b7e805 – < 7dc211c1159d991db609bdf4b0fb9033c04adcbc
  • Linux · Linux

    • affected 5.1
    • unaffected < 5.1
    • unaffected 6.1.160 – ≤ 6.1.*
    • unaffected 6.6.120 – ≤ 6.6.*
    • unaffected 6.12.63 – ≤ 6.12.*
    • unaffected 6.17.13 – ≤ 6.17.*
    • unaffected 6.18.2 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .