<?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://db.gcve.eu</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>Mon, 19 Oct 2026 17:08:08 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-98851</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-98851</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: nft_flow_offload: drop flowtable reference on init error path&lt;/p&gt;
&lt;p&gt;nft_flow_offload_init() bumps the flowtable use count with
nft_use_inc() before calling nf_ct_netns_get().  When the latter
fails, the error is returned as-is and the reference is leaked.&lt;/p&gt;
&lt;p&gt;The upper layers do not balance it either: nf_tables_newexpr()
clears expr-&amp;gt;ops when the expression init callback fails, so the
nft_expr_more() iteration in nft_rule_expr_deactivate() and
nf_tables_rule_destroy() stops right before the failed expression
and its -&amp;gt;destroy callback, which would drop the reference, never
runs.&lt;/p&gt;
&lt;p&gt;Each failed rule addition therefore leaks one flowtable reference
and the flowtable can no longer be removed: NFT_MSG_DELFLOWTABLE
keeps reporting -EBUSY even though no rule references it.&lt;/p&gt;
&lt;p&gt;Save the nf_ct_netns_get() return value and undo the nft_use_inc()
when it fails, restoring the inc/dec pairing within
nft_flow_offload_init() itself.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: nft_flow_offload: drop flowtable reference on init error path&lt;/p&gt;
&lt;p&gt;nft_flow_offload_init() bumps the flowtable use count with
nft_use_inc() before calling nf_ct_netns_get().  When the latter
fails, the error is returned as-is and the reference is leaked.&lt;/p&gt;
&lt;p&gt;The upper layers do not balance it either: nf_tables_newexpr()
clears expr-&amp;gt;ops when the expression init callback fails, so the
nft_expr_more() iteration in nft_rule_expr_deactivate() and
nf_tables_rule_destroy() stops right before the failed expression
and its -&amp;gt;destroy callback, which would drop the reference, never
runs.&lt;/p&gt;
&lt;p&gt;Each failed rule addition therefore leaks one flowtable reference
and the flowtable can no longer be removed: NFT_MSG_DELFLOWTABLE
keeps reporting -EBUSY even though no rule references it.&lt;/p&gt;
&lt;p&gt;Save the nf_ct_netns_get() return value and undo the nft_use_inc()
when it fails, restoring the inc/dec pairing within
nft_flow_offload_init() itself.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-98851</guid>
    </item>
    <item>
      <title>GHSA-95vh-jxqc-h2w9</title>
      <link>https://db.gcve.eu/vuln/ghsa-95vh-jxqc-h2w9</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: nft_flow_offload: drop flowtable reference on init error path&lt;/p&gt;
&lt;p&gt;nft_flow_offload_init() bumps the flowtable use count with
nft_use_inc() before calling nf_ct_netns_get().  When the latter
fails, the error is returned as-is and the reference is leaked.&lt;/p&gt;
&lt;p&gt;The upper layers do not balance it either: nf_tables_newexpr()
clears expr-&amp;gt;ops when the expression init callback fails, so the
nft_expr_more() iteration in nft_rule_expr_deactivate() and
nf_tables_rule_destroy() stops right before the failed expression
and its -&amp;gt;destroy callback, which would drop the reference, never
runs.&lt;/p&gt;
&lt;p&gt;Each failed rule addition therefore leaks one flowtable reference
and the flowtable can no longer be removed: NFT_MSG_DELFLOWTABLE
keeps reporting -EBUSY even though no rule references it.&lt;/p&gt;
&lt;p&gt;Save the nf_ct_netns_get() return value and undo the nft_use_inc()
when it fails, restoring the inc/dec pairing within
nft_flow_offload_init() itself.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: nft_flow_offload: drop flowtable reference on init error path&lt;/p&gt;
&lt;p&gt;nft_flow_offload_init() bumps the flowtable use count with
nft_use_inc() before calling nf_ct_netns_get().  When the latter
fails, the error is returned as-is and the reference is leaked.&lt;/p&gt;
&lt;p&gt;The upper layers do not balance it either: nf_tables_newexpr()
clears expr-&amp;gt;ops when the expression init callback fails, so the
nft_expr_more() iteration in nft_rule_expr_deactivate() and
nf_tables_rule_destroy() stops right before the failed expression
and its -&amp;gt;destroy callback, which would drop the reference, never
runs.&lt;/p&gt;
&lt;p&gt;Each failed rule addition therefore leaks one flowtable reference
and the flowtable can no longer be removed: NFT_MSG_DELFLOWTABLE
keeps reporting -EBUSY even though no rule references it.&lt;/p&gt;
&lt;p&gt;Save the nf_ct_netns_get() return value and undo the nft_use_inc()
when it fails, restoring the inc/dec pairing within
nft_flow_offload_init() itself.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-95vh-jxqc-h2w9</guid>
    </item>
  </channel>
</rss>
