<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-27T15:09:53.127705+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/fkie_cve-2026-98899</id>
    <title>fkie_cve-2026-98899</title>
    <updated>2026-10-27T15:09:53.168689+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>netfilter: ipset: mark the rcu locked areas properly</p>
<p>When we bump the uref counter, there's no need to keep
the rcu lock because the referred hash table can't
disappear. Also, from the same reason in mtype_gc we
need the rcu lock and not a spinlock.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-98899"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-ffrw-gp84-hx8m</id>
    <title>GHSA-ffrw-gp84-hx8m</title>
    <updated>2026-10-27T15:09:53.168781+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>netfilter: ipset: mark the rcu locked areas properly</p>
<p>When we bump the uref counter, there's no need to keep
the rcu lock because the referred hash table can't
disappear. Also, from the same reason in mtype_gc we
need the rcu lock and not a spinlock.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-ffrw-gp84-hx8m"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/msrc_cve-2026-98899</id>
    <title>msrc_CVE-2026-98899 — netfilter: ipset: mark the rcu locked areas properly</title>
    <updated>2026-10-27T15:09:53.168804+00:00</updated>
    <content>msrc_CVE-2026-98899</content>
    <link href="https://db.gcve.eu/vuln/msrc_cve-2026-98899"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ubuntu-cve-2026-98899</id>
    <title>UBUNTU-CVE-2026-98899</title>
    <updated>2026-10-27T15:09:53.168826+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 257 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: netfilter: ipset: mark the rcu locked areas properly When we bump the uref counter, there's no need to keep the rcu lock because the referred hash table can't disappear. Also, from the same reason in mtype_gc we need the rcu lock and not a spinlock.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ubuntu-cve-2026-98899"/>
  </entry>
</feed>
