<?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 21:35:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68462 — bpf: Reject negative const offsets for buffer pointers</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-68462</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: Reject negative const offsets for buffer pointers&lt;/p&gt;
&lt;p&gt;The verifier rejects variable offsets for PTR_TO_TP_BUFFER and PTR_TO_BUF
accesses, but it currently accepts a constant negative offset produced by
pointer arithmetic.&lt;/p&gt;
&lt;p&gt;Commit 022ac0750883 (&amp;#34;bpf: use reg-&amp;gt;var_off instead of reg-&amp;gt;off for
pointers&amp;#34;) moved constant pointer offsets from reg-&amp;gt;off to reg-&amp;gt;var_off.
However, __check_buffer_access() continued to check only the instruction
offset. An access with reg-&amp;gt;var_off equal to -8 and an instruction offset
of zero therefore passes verification.&lt;/p&gt;
&lt;p&gt;For writable raw tracepoints, the access end is also calculated from the
unsigned reg-&amp;gt;var_off.value. An eight-byte access starting at -8 wraps
the calculated end to zero, allowing the program to load and attach
without increasing max_tp_access.&lt;/p&gt;
&lt;p&gt;After ensuring that reg-&amp;gt;var_off is constant, calculate the effective
access start using signed arithmetic and reject it when it is negative.
Use the validated start to calculate the access end for both
PTR_TO_TP_BUFFER and PTR_TO_BUF.&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: Reject negative const offsets for buffer pointers&lt;/p&gt;
&lt;p&gt;The verifier rejects variable offsets for PTR_TO_TP_BUFFER and PTR_TO_BUF
accesses, but it currently accepts a constant negative offset produced by
pointer arithmetic.&lt;/p&gt;
&lt;p&gt;Commit 022ac0750883 (&amp;#34;bpf: use reg-&amp;gt;var_off instead of reg-&amp;gt;off for
pointers&amp;#34;) moved constant pointer offsets from reg-&amp;gt;off to reg-&amp;gt;var_off.
However, __check_buffer_access() continued to check only the instruction
offset. An access with reg-&amp;gt;var_off equal to -8 and an instruction offset
of zero therefore passes verification.&lt;/p&gt;
&lt;p&gt;For writable raw tracepoints, the access end is also calculated from the
unsigned reg-&amp;gt;var_off.value. An eight-byte access starting at -8 wraps
the calculated end to zero, allowing the program to load and attach
without increasing max_tp_access.&lt;/p&gt;
&lt;p&gt;After ensuring that reg-&amp;gt;var_off is constant, calculate the effective
access start using signed arithmetic and reject it when it is negative.
Use the validated start to calculate the access end for both
PTR_TO_TP_BUFFER and PTR_TO_BUF.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-68462</guid>
    </item>
  </channel>
</rss>
