<?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://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T02:24:37.123698+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" 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://127.0.0.1:10001/vuln/bell-cve-2025-21682</id>
    <title>BELL-CVE-2025-21682</title>
    <updated>2026-11-21T02:24:37.138116+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2025-21682"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2025-avi-0133</id>
    <title>certfr-2025-avi-0133 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Elles permettent à un attaquant de provoqu…</title>
    <updated>2026-11-21T02:24:37.138162+00:00</updated>
    <content>certfr-2025-avi-0133</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2025-avi-0133"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2025-1959</id>
    <title>OESA-2025-1959 — kernel security update</title>
    <updated>2026-11-21T02:24:37.138180+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:24.03-LTS: kernel</p>
<p>The Linux Kernel, the operating system core itself.

Security Fix(es):</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>xfrm: state: fix out-of-bounds read during lookup</p>
<p>lookup and resize can run in parallel.</p>
<p>The xfrm_state_hash_generation seqlock ensures a retry, but the hash
functions can observe a hmask value that is too large for the new hlist
array.</p>
<p>rehash does:
  rcu_assign_pointer(net-&amp;gt;xfrm.state_bydst, ndst) [..]
  net-&amp;gt;xfrm.state_hmask = nhashmask;</p>
<p>While state lookup does:
  h = xfrm_dst_hash(net, daddr, saddr, tmpl-&amp;gt;reqid, encap_family);
  hlist_for_each_entry_rcu(x, net-&amp;gt;xfrm.state_bydst + h, bydst) {</p>
<p>This is only safe in case the update to state_bydst is larger than
net-&amp;gt;xfrm.xfrm_state_hmask (or if the lookup function gets
serialized via state spinlock again).</p>
<p>Fix this by prefetching state_hmask and the associated pointers.
The xfrm_state_hash_generation seqlock retry will ensure that the pointer
and the hmask will be consistent.</p>
<p>The existing helpers, like xfrm_dst_hash(), are now unsafe for RCU side,
add lockdep assertions to document that they are only safe for insert
side.</p>
<p>xfrm_state_lookup_byaddr() uses the spinlock rather than RCU.
AFAICS this is an oversight from back when state lookup was converted to
RCU, this lock should be replaced with RCU in a future patch.(CVE-2024-57982)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>eth: bnxt: always recalculate features after XDP clearing, fix n…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2025-1959"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21682</id>
    <title>UBUNTU-CVE-2025-21682</title>
    <updated>2026-11-21T02:24:37.138489+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 171 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: eth: bnxt: always recalculate features after XDP clearing, fix null-deref Recalculate features when XDP is detached. Before:   # ip li set dev eth0 xdp obj xdp_dummy.bpf.o sec xdp   # ip li set dev eth0 xdp off   # ethtool -k eth0 | grep gro   rx-gro-hw: off [requested on] After:   # ip li set dev eth0 xdp obj xdp_dummy.bpf.o sec xdp   # ip li set dev eth0 xdp off   # ethtool -k eth0 | grep gro   rx-gro-hw: on The fact that HW-GRO doesn't get re-enabled automatically is just a minor annoyance. The real issue is that the features will randomly come back during another reconfiguration which just happens to invoke netdev_update_features(). The driver doesn't handle reconfiguring two things at a time very robustly. Starting with commit 98ba1d931f61 ("bnxt_en: Fix RSS logic in __bnxt_reserve_rings()") we only reconfigure the RSS hash table if the "effective" number of Rx rings has changed. If HW-GRO is enabled "effective" number of rings is 2x what user sees. So if we are in the bad state, with HW-GRO re-enablement "pending" after XDP off, and we lower the rings by / 2 - the HW-GRO rings doing 2x and the ethtool -L doing / 2 may cancel each other out, and the:   if (old_rx_rings != bp-&gt;hw_resc.resv_rx_rings &amp;&amp; condition in __bnxt_reserve_rings() will be false. The RSS map won't get updated, and we'll crash with:   BUG: kernel NULL pointer dereference, address: 0000000000000168   RIP: 0010:__bnxt_hwrm_vnic_set_rss…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21682"/>
  </entry>
</feed>
