<?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>Wed, 30 Sep 2026 02:55:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68144 — phonet: pep: fix use-after-free in pep_get_sb()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-68144</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;phonet: pep: fix use-after-free in pep_get_sb()&lt;/p&gt;
&lt;p&gt;pep_get_sb() doesn&amp;#39;t consider that pskb_may_pull() might have relocated
the skb data, and continue to access the older pointer, causing UAF.&lt;/p&gt;
&lt;p&gt;Reproduced under KASAN:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in pep_get_sb+0x234/0x3b0
  Read of size 1 at addr ff11000105510f50 by task repro/157
   pep_get_sb+0x234/0x3b0
   pipe_handler_do_rcv+0x5f7/0xa10
   pep_do_rcv+0x203/0x410
   __sk_receive_skb+0x471/0x4a0
   phonet_rcv+0x5b3/0x6c0
   __netif_receive_skb+0xcc/0x1d0&lt;/p&gt;
&lt;p&gt;Refetch the header with skb_header_pointer() after pskb_may_pull(), so
the possibly stale pointer is no longer dereferenced. There are better
ways to solve this, but, this is the less instrusive one.&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;phonet: pep: fix use-after-free in pep_get_sb()&lt;/p&gt;
&lt;p&gt;pep_get_sb() doesn&amp;#39;t consider that pskb_may_pull() might have relocated
the skb data, and continue to access the older pointer, causing UAF.&lt;/p&gt;
&lt;p&gt;Reproduced under KASAN:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in pep_get_sb+0x234/0x3b0
  Read of size 1 at addr ff11000105510f50 by task repro/157
   pep_get_sb+0x234/0x3b0
   pipe_handler_do_rcv+0x5f7/0xa10
   pep_do_rcv+0x203/0x410
   __sk_receive_skb+0x471/0x4a0
   phonet_rcv+0x5b3/0x6c0
   __netif_receive_skb+0xcc/0x1d0&lt;/p&gt;
&lt;p&gt;Refetch the header with skb_header_pointer() after pskb_may_pull(), so
the possibly stale pointer is no longer dereferenced. There are better
ways to solve this, but, this is the less instrusive one.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-68144</guid>
    </item>
  </channel>
</rss>
