<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 01 Oct 2026 20:08:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-68742 — bpf: Fix invalid prog-&gt;stats access when update_effective_progs fails</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-68742</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Fix invalid prog-&amp;gt;stats access when update_effective_progs fails&lt;/p&gt;
&lt;p&gt;Syzkaller triggers an invalid memory access issue following fault
injection in update_effective_progs. The issue can be described as
follows:&lt;/p&gt;
&lt;p&gt;__cgroup_bpf_detach
  update_effective_progs
    compute_effective_progs
      bpf_prog_array_alloc &amp;lt;-- fault inject
  purge_effective_progs
    /* change to dummy_bpf_prog */
    array-&amp;gt;items[index] = &amp;amp;dummy_bpf_prog.prog&lt;/p&gt;
&lt;p&gt;---softirq start---
__do_softirq
  ...
    __cgroup_bpf_run_filter_skb
      __bpf_prog_run_save_cb
        bpf_prog_run
          stats = this_cpu_ptr(prog-&amp;gt;stats)
          /* invalid memory access */
          flags = u64_stats_update_begin_irqsave(&amp;amp;stats-&amp;gt;syncp)
---softirq end---&lt;/p&gt;
&lt;p&gt;static_branch_dec(&amp;amp;cgroup_bpf_enabled_key[atype])&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;To fix it, skip updating stats when stats is NULL.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Fix invalid prog-&amp;gt;stats access when update_effective_progs fails&lt;/p&gt;
&lt;p&gt;Syzkaller triggers an invalid memory access issue following fault
injection in update_effective_progs. The issue can be described as
follows:&lt;/p&gt;
&lt;p&gt;__cgroup_bpf_detach
  update_effective_progs
    compute_effective_progs
      bpf_prog_array_alloc &amp;lt;-- fault inject
  purge_effective_progs
    /* change to dummy_bpf_prog */
    array-&amp;gt;items[index] = &amp;amp;dummy_bpf_prog.prog&lt;/p&gt;
&lt;p&gt;---softirq start---
__do_softirq
  ...
    __cgroup_bpf_run_filter_skb
      __bpf_prog_run_save_cb
        bpf_prog_run
          stats = this_cpu_ptr(prog-&amp;gt;stats)
          /* invalid memory access */
          flags = u64_stats_update_begin_irqsave(&amp;amp;stats-&amp;gt;syncp)
---softirq end---&lt;/p&gt;
&lt;p&gt;static_branch_dec(&amp;amp;cgroup_bpf_enabled_key[atype])&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;To fix it, skip updating stats when stats is NULL.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-68742</guid>
    </item>
  </channel>
</rss>
