<?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-20T22:47:45.170258+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-38048</id>
    <title>BELL-CVE-2025-38048</title>
    <updated>2026-11-20T22:47:45.187563+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-38048"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2025-avi-0698</id>
    <title>certfr-2025-avi-0698 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
    <updated>2026-11-20T22:47:45.187617+00:00</updated>
    <content>certfr-2025-avi-0698</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2025-avi-0698"/>
  </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-20T22:47:45.187636+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-38048</id>
    <title>UBUNTU-CVE-2025-38048</title>
    <updated>2026-11-20T22:47:45.187944+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:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 159 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: virtio_ring: Fix data race by tagging event_triggered as racy for KCSAN syzbot reports a data-race when accessing the event_triggered, here is the simplified stack when the issue occurred: ================================================================== BUG: KCSAN: data-race in virtqueue_disable_cb / virtqueue_enable_cb_delayed write to 0xffff8881025bc452 of 1 bytes by task 3288 on cpu 0:  virtqueue_enable_cb_delayed+0x42/0x3c0 drivers/virtio/virtio_ring.c:2653  start_xmit+0x230/0x1310 drivers/net/virtio_net.c:3264  __netdev_start_xmit include/linux/netdevice.h:5151 [inline]  netdev_start_xmit include/linux/netdevice.h:5160 [inline]  xmit_one net/core/dev.c:3800 [inline] read to 0xffff8881025bc452 of 1 bytes by interrupt on cpu 1:  virtqueue_disable_cb_split drivers/virtio/virtio_ring.c:880 [inline]  virtqueue_disable_cb+0x92/0x180 drivers/virtio/virtio_ring.c:2566  skb_xmit_done+0x5f/0x140 drivers/net/virtio_net.c:777  vring_interrupt+0x161/0x190 drivers/virtio/virtio_ring.c:2715  __handle_irq_event_percpu+0x95/0x490 kernel/irq/handle.c:158  handle_irq_event_percpu kernel/irq/handle.c:193 [inline] value changed: 0x01 -&gt; 0x00 ================================================================== When the data race occurs, the function virtqueue_enable_cb_delayed() sets event_triggered to false, and virtqueue_disable_cb_split/packed() reads it as false due to the race condition. Since event_triggered is an unre…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38048"/>
  </entry>
</feed>
