<?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-21T05:01:56.060199+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-2026-53358</id>
    <title>BELL-CVE-2026-53358</title>
    <updated>2026-11-21T05:01:56.086412+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-2026-53358"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-0926</id>
    <title>certfr-2026-avi-0926 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
    <updated>2026-11-21T05:01:56.086451+00:00</updated>
    <content>certfr-2026-avi-0926</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-0926"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2026-3204</id>
    <title>OESA-2026-3204 — kernel security update</title>
    <updated>2026-11-21T05:01:56.086467+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:24.03-LTS-SP1: 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>wifi: rtw88: Use devm_kmemdup() in rtw_set_supported_band()</p>
<p>Simplify the code by using device managed memory allocations.</p>
<p>This also fixes a memory leak in rtw_register_hw(). The supported bands
were not freed in the error path.</p>
<p>Copied from commit 145df52a8671 (&amp;quot;wifi: rtw89: Convert
rtw89_core_set_supported_band to use devm_*&amp;quot;).(CVE-2025-71273)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>xfrm: hold dev ref until after transport_finish NF_HOOK</p>
<p>After async crypto completes, xfrm_input_resume() calls dev_put()
immediately on re-entry before the skb reaches transport_finish.
The skb-&amp;gt;dev pointer is then used inside NF_HOOK and its okfn,
which can race with device teardown.</p>
<p>Remove the dev_put from the async resumption entry and instead
drop the reference after the NF_HOOK call in transport_finish,
using a saved device pointer since NF_HOOK may consume the skb.
This covers NF_DROP, NF_QUEUE and NF_STOLEN paths that skip
the okfn.</p>
<p>For non-transport exits (decaps, gro, drop) and secondary
async return points, release the reference inline when
async is set.(CVE-2026-31663)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>x86: shadow stacks: proper error handling for mmap lock</p>
<p>김영민 reports that shstk_pop_sigframe() doesn&amp;apos;t check for errors from
mmap_read_lock_killable(), whic…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2026-3204"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53358</id>
    <title>UBUNTU-CVE-2026-53358</title>
    <updated>2026-11-21T05:01:56.086842+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 256 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: use chan timer to close channels in cleanup_listen() l2cap_chan_close() removes the channel from conn-&gt;chan_l, which must be done under conn-&gt;lock.  cleanup_listen() runs under the parent sk_lock, so acquiring conn-&gt;lock would invert the established conn-&gt;lock -&gt; chan-&gt;lock -&gt; sk_lock order. Instead of calling l2cap_chan_close() directly, schedule l2cap_chan_timeout with delay 0 to close the channel asynchronously.  The timeout handler already acquires conn-&gt;lock and chan-&gt;lock in the correct order. The timer is only armed when chan-&gt;conn is still set: if it is already NULL, l2cap_conn_del() has already processed this channel (l2cap_chan_del + l2cap_sock_teardown_cb + l2cap_sock_close_cb), so there is nothing left to do.  If l2cap_conn_del() races in after the timer is armed, __clear_chan_timer() inside l2cap_chan_del() cancels it; if the timer has already fired, the handler returns harmlessly because chan-&gt;conn was cleared.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53358"/>
  </entry>
</feed>
