<?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>Sat, 03 Oct 2026 22:51:02 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43254 — ovpn: tcp - fix packet extraction from stream</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-43254</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;ovpn: tcp - fix packet extraction from stream&lt;/p&gt;
&lt;p&gt;When processing TCP stream data in ovpn_tcp_recv, we receive large
cloned skbs from __strp_rcv that may contain multiple coalesced packets.
The current implementation has two bugs:&lt;/p&gt;
&lt;p&gt;1. Header offset overflow: Using pskb_pull with large offsets on
   coalesced skbs causes skb-&amp;gt;data - skb-&amp;gt;head to exceed the u16 storage
   of skb-&amp;gt;network_header. This causes skb_reset_network_header to fail
   on the inner decapsulated packet, resulting in packet drops.&lt;/p&gt;
&lt;p&gt;2. Unaligned protocol headers: Extracting packets from arbitrary
   positions within the coalesced TCP stream provides no alignment
   guarantees for the packet data causing performance penalties on
   architectures without efficient unaligned access. Additionally,
   openvpn&amp;#39;s 2-byte length prefix on TCP packets causes the subsequent
   4-byte opcode and packet ID fields to be inherently misaligned.&lt;/p&gt;
&lt;p&gt;Fix both issues by allocating a new skb for each openvpn packet and
using skb_copy_bits to extract only the packet content into the new
buffer, skipping the 2-byte length prefix. Also, check the length before
invoking the function that performs the allocation to avoid creating an
invalid skb.&lt;/p&gt;
&lt;p&gt;If the packet has to be forwarded to userspace the 2-byte prefix can be
pushed to the head safely, without misalignment.&lt;/p&gt;
&lt;p&gt;As a side effect, this approach also avoids the expensive linearization
that pskb_pull triggers on clone…&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;ovpn: tcp - fix packet extraction from stream&lt;/p&gt;
&lt;p&gt;When processing TCP stream data in ovpn_tcp_recv, we receive large
cloned skbs from __strp_rcv that may contain multiple coalesced packets.
The current implementation has two bugs:&lt;/p&gt;
&lt;p&gt;1. Header offset overflow: Using pskb_pull with large offsets on
   coalesced skbs causes skb-&amp;gt;data - skb-&amp;gt;head to exceed the u16 storage
   of skb-&amp;gt;network_header. This causes skb_reset_network_header to fail
   on the inner decapsulated packet, resulting in packet drops.&lt;/p&gt;
&lt;p&gt;2. Unaligned protocol headers: Extracting packets from arbitrary
   positions within the coalesced TCP stream provides no alignment
   guarantees for the packet data causing performance penalties on
   architectures without efficient unaligned access. Additionally,
   openvpn&amp;#39;s 2-byte length prefix on TCP packets causes the subsequent
   4-byte opcode and packet ID fields to be inherently misaligned.&lt;/p&gt;
&lt;p&gt;Fix both issues by allocating a new skb for each openvpn packet and
using skb_copy_bits to extract only the packet content into the new
buffer, skipping the 2-byte length prefix. Also, check the length before
invoking the function that performs the allocation to avoid creating an
invalid skb.&lt;/p&gt;
&lt;p&gt;If the packet has to be forwarded to userspace the 2-byte prefix can be
pushed to the head safely, without misalignment.&lt;/p&gt;
&lt;p&gt;As a side effect, this approach also avoids the expensive linearization
that pskb_pull triggers on clone…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-43254</guid>
    </item>
  </channel>
</rss>
