<?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-01T07:07:11.009459+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-2022-49622</id>
    <title>CVE-2022-49622 — netfilter: nf_tables: avoid skb access on nf_stolen</title>
    <updated>2026-10-01T07:07:12.410800+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>netfilter: nf_tables: avoid skb access on nf_stolen</p>
<p>When verdict is NF_STOLEN, the skb might have been freed.</p>
<p>When tracing is enabled, this can result in a use-after-free:
1. access to skb-&gt;nf_trace
2. access to skb-&gt;mark
3. computation of trace id
4. dump of packet payload</p>
<p>To avoid 1, keep a cached copy of skb-&gt;nf_trace in the
trace state struct.
Refresh this copy whenever verdict is != STOLEN.</p>
<p>Avoid 2 by skipping skb-&gt;mark access if verdict is STOLEN.</p>
<p>3 is avoided by precomputing the trace id.</p>
<p>Only dump the packet when verdict is not "STOLEN".</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2022-49622"/>
  </entry>
</feed>
