<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T04:45:54.918882+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-43254</id>
    <title>CVE-2026-43254 — ovpn: tcp - fix packet extraction from stream</title>
    <updated>2026-10-04T04:45:54.933687+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ovpn: tcp - fix packet extraction from stream</p>
<p>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:</p>
<p>1. Header offset overflow: Using pskb_pull with large offsets on
   coalesced skbs causes skb-&gt;data - skb-&gt;head to exceed the u16 storage
   of skb-&gt;network_header. This causes skb_reset_network_header to fail
   on the inner decapsulated packet, resulting in packet drops.</p>
<p>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's 2-byte length prefix on TCP packets causes the subsequent
   4-byte opcode and packet ID fields to be inherently misaligned.</p>
<p>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.</p>
<p>If the packet has to be forwarded to userspace the 2-byte prefix can be
pushed to the head safely, without misalignment.</p>
<p>As a side effect, this approach also avoids the expensive linearization
that pskb_pull triggers on clone…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-43254"/>
  </entry>
</feed>
