<?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>Tue, 29 Sep 2026 12:56:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98132 — bpf: don't downgrade half-dead scalar zero spills to STACK_ZERO</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-98132</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: don&amp;#39;t downgrade half-dead scalar zero spills to STACK_ZERO&lt;/p&gt;
&lt;p&gt;states.c:__clean_func_state() can downgrade scalar zero spill to
STACK_ZERO in the following case:&lt;/p&gt;
&lt;p&gt;*(u64 *)(r10 - 8) = 0;
  ... checkpoint ...
  r1 = *(u32 *)(r10 - 4);
  ... no reads from r10-8 ...&lt;/p&gt;
&lt;p&gt;Here 4 bytes at r10-8 are dead and verifier changes scalar spill to a
combination: 0000pppp (p stands for poison). Such a change breaks
precision propagation chains. All places that produce STACK_ZERO
should call bpf_mark_chain_precision() for the zero source.&lt;/p&gt;
&lt;p&gt;This patch fixes the bug in a simplest way possible:
avoids converting stack spills of zero to STACK_ZERO.
Two smarter approaches are possible:
- do bpf_mark_chain_precision() from __clean_func_state()
- check slot liveness information in check_stack_write_fixed_off()&lt;/p&gt;
&lt;p&gt;I investigated both and the changes required are a bit tricky,
hence go with a simple fix for the time being.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: don&amp;#39;t downgrade half-dead scalar zero spills to STACK_ZERO&lt;/p&gt;
&lt;p&gt;states.c:__clean_func_state() can downgrade scalar zero spill to
STACK_ZERO in the following case:&lt;/p&gt;
&lt;p&gt;*(u64 *)(r10 - 8) = 0;
  ... checkpoint ...
  r1 = *(u32 *)(r10 - 4);
  ... no reads from r10-8 ...&lt;/p&gt;
&lt;p&gt;Here 4 bytes at r10-8 are dead and verifier changes scalar spill to a
combination: 0000pppp (p stands for poison). Such a change breaks
precision propagation chains. All places that produce STACK_ZERO
should call bpf_mark_chain_precision() for the zero source.&lt;/p&gt;
&lt;p&gt;This patch fixes the bug in a simplest way possible:
avoids converting stack spills of zero to STACK_ZERO.
Two smarter approaches are possible:
- do bpf_mark_chain_precision() from __clean_func_state()
- check slot liveness information in check_stack_write_fixed_off()&lt;/p&gt;
&lt;p&gt;I investigated both and the changes required are a bit tricky,
hence go with a simple fix for the time being.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-98132</guid>
    </item>
  </channel>
</rss>
