<?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 13:03:08 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68302 — amt: re-read skb header pointers after every pull</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-68302</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;amt: re-read skb header pointers after every pull&lt;/p&gt;
&lt;p&gt;Several AMT receive and transmit paths cache a pointer into the skb head
(ip_hdr(), ipv6_hdr(), eth_hdr() or the AMT message header) and then call
a helper that can reallocate that head before the cached pointer is used
again.  pskb_may_pull(), ip_mc_may_pull(), ipv6_mc_may_pull(),
iptunnel_pull_header(), ip_mc_check_igmp() and ipv6_mc_check_mld() can all
free the old head and move the data, so a pointer taken before the call
dangles afterwards and the later access is a use-after-free of the freed
head.&lt;/p&gt;
&lt;p&gt;The affected sites are:&lt;/p&gt;
&lt;p&gt;amt_rcv() caches ip_hdr() before amt_parse_type() pulls, then reads
  iph-&amp;gt;saddr.&lt;/p&gt;
&lt;p&gt;amt_dev_xmit() caches ip_hdr()/ipv6_hdr() before ip_mc_check_igmp()/
  ipv6_mc_check_mld() and pskb_may_pull(), then reads the group address.&lt;/p&gt;
&lt;p&gt;amt_multicast_data_handler() caches eth_hdr() before pskb_may_pull(),
  then writes the L2 header.&lt;/p&gt;
&lt;p&gt;amt_membership_query_handler() caches the AMT header, the outer and
  inner eth_hdr() and ip_hdr() before iptunnel_pull_header() and several
  pulls, then reads and writes them.&lt;/p&gt;
&lt;p&gt;amt_igmpv3_report_handler() and amt_mldv2_report_handler() cache
  ip_hdr()/ipv6_hdr() and the current group record and read the record
  count from the report header inside the record loop, across the
  *_mc_may_pull() calls.&lt;/p&gt;
&lt;p&gt;amt_update_handler() caches ip_hdr() and the AMT membership-update
  header before pskb_may_pull(),…&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;amt: re-read skb header pointers after every pull&lt;/p&gt;
&lt;p&gt;Several AMT receive and transmit paths cache a pointer into the skb head
(ip_hdr(), ipv6_hdr(), eth_hdr() or the AMT message header) and then call
a helper that can reallocate that head before the cached pointer is used
again.  pskb_may_pull(), ip_mc_may_pull(), ipv6_mc_may_pull(),
iptunnel_pull_header(), ip_mc_check_igmp() and ipv6_mc_check_mld() can all
free the old head and move the data, so a pointer taken before the call
dangles afterwards and the later access is a use-after-free of the freed
head.&lt;/p&gt;
&lt;p&gt;The affected sites are:&lt;/p&gt;
&lt;p&gt;amt_rcv() caches ip_hdr() before amt_parse_type() pulls, then reads
  iph-&amp;gt;saddr.&lt;/p&gt;
&lt;p&gt;amt_dev_xmit() caches ip_hdr()/ipv6_hdr() before ip_mc_check_igmp()/
  ipv6_mc_check_mld() and pskb_may_pull(), then reads the group address.&lt;/p&gt;
&lt;p&gt;amt_multicast_data_handler() caches eth_hdr() before pskb_may_pull(),
  then writes the L2 header.&lt;/p&gt;
&lt;p&gt;amt_membership_query_handler() caches the AMT header, the outer and
  inner eth_hdr() and ip_hdr() before iptunnel_pull_header() and several
  pulls, then reads and writes them.&lt;/p&gt;
&lt;p&gt;amt_igmpv3_report_handler() and amt_mldv2_report_handler() cache
  ip_hdr()/ipv6_hdr() and the current group record and read the record
  count from the report header inside the record loop, across the
  *_mc_may_pull() calls.&lt;/p&gt;
&lt;p&gt;amt_update_handler() caches ip_hdr() and the AMT membership-update
  header before pskb_may_pull(),…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-68302</guid>
    </item>
  </channel>
</rss>
