LiveActive security incident?Get immediate response
CVE Record

CVE-2025-68742: bpf: Fix invalid prog->stats access when update_effective_progs fails

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can cause invalid memory access in BPF/cgroup handling after an internal update failure. The public record describes a Syzkaller fault-injection finding, not confirmed real-world exploitation. Business impact is uncertain, but kernel faults can affect availability, so affected Linux estates should track vendor kernel updates.

Executive priority

Treat as a kernel maintenance item with uncertain severity. Prioritize patch confirmation for internet-facing, multi-tenant, or operationally critical Linux systems, but do not classify as actively exploited based on the provided evidence.

Technical view

The bug occurs when update_effective_progs fails, purge_effective_progs substitutes dummy_bpf_prog.prog, and a softirq path later accesses prog->stats. Because dummy_bpf_prog.prog may have NULL stats, bpf_prog_run can dereference invalid memory. The stated fix is to skip stats updates when stats is NULL.

Likely exposure

Exposure is limited to Linux systems running affected kernel builds with the vulnerable BPF/cgroup code present. The bundle lists Linux as affected and provides stable-kernel fix references. Actual exposure depends on distribution backports, vendor kernel packaging, and any Siemens product-specific applicability.

Exploitation context

No active exploitation is supported by the provided sources. The CVE is not listed as KEV in the bundle. The reported trigger came from Syzkaller with fault injection, so practical exploitability and attacker prerequisites are not established here.

Researcher notes

The key condition is a failure in update_effective_progs followed by dummy_bpf_prog substitution and a softirq BPF execution path. The source description identifies NULL stats handling as the fix. CVSS, CWE, exploitability, and attacker prerequisites are not provided.

Mitigation direction

  • Apply vendor kernel updates that include the referenced Linux stable fixes.
  • Review distribution advisories for CVE-2025-68742 and matching kernel package versions.
  • For Siemens environments, review SSA-019113 for product-specific guidance.
  • If updates are unavailable, follow vendor guidance rather than applying speculative mitigations.

Validation and detection

  • Inventory Linux kernel versions and vendor package build identifiers across affected assets.
  • Confirm whether installed kernels include one of the referenced stable fixes or backports.
  • Check vendor advisories for exact affected and fixed package versions.
  • Review Siemens SSA-019113 if Siemens products are deployed.
Prepared
Confidence
medium
Sources
9

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-2025-68742 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
1ADP providers
8Source links

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

siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux492ecee892c2a4ba6a14903d5d586ff750b7e805, 492ecee892c2a4ba6a14903d5d586ff750b7e805, 492ecee892c2a4ba6a14903d5d586ff750b7e805, 492ecee892c2a4ba6a14903d5d586ff750b7e805, 492ecee892c2a4ba6a14903d5d586ff750b7e805, 492ecee892c2a4ba6a14903d5d586ff750b7e805unaffected
LinuxLinux5.1, 0, 6.1.160, 6.6.120, 6.12.63, 6.17.13, 6.18.2, 6.19affected
Weakness

CWE details

No CWE listed

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