<?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://127.0.0.1:10001</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>Sat, 21 Nov 2026 03:24:57 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-23150</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-23150</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2026-23150</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0316 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0316</link>
      <description>certfr-2026-avi-0316</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0316</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-23150</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-23150</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 232 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: Fix memleak in nfc_llcp_send_ui_frame(). syzbot reported various memory leaks related to NFC, struct nfc_llcp_sock, sk_buff, nfc_dev, etc. [0] The leading log hinted that nfc_llcp_send_ui_frame() failed to allocate skb due to sock_error(sk) being -ENXIO. ENXIO is set by nfc_llcp_socket_release() when struct nfc_llcp_local is destroyed by local_cleanup(). The problem is that there is no synchronisation between nfc_llcp_send_ui_frame() and local_cleanup(), and skb could be put into local-&amp;gt;tx_queue after it was purged in local_cleanup():   CPU1                          CPU2   ----                          ----   nfc_llcp_send_ui_frame()      local_cleanup()   |- do {                       &amp;#39;      |- pdu = nfc_alloc_send_skb(..., &amp;amp;err)      |                          .      |                          |- nfc_llcp_socket_release(local, false, ENXIO);      |                          |- skb_queue_purge(&amp;amp;local-&amp;gt;tx_queue); |      |                          &amp;#39; |      |- skb_queue_tail(&amp;amp;local-&amp;gt;tx_queue, pdu); |     ... |      |- pdu = nfc_alloc_send_skb(..., &amp;amp;err) | ^._________________________________.&amp;#39; local_cleanup() is called for struct nfc_llcp_local only after nfc_llcp_remove_local() unlinks it from llcp_devices. If we hold local-&amp;gt;tx_queue.lock then, we can synchronise the thread and nfc_llcp_send_ui_frame(). Let&amp;#39;s do that and check list_empty(&amp;amp;local-&amp;gt;list) before queuing skb to local-&amp;gt;tx_queue in nfc_llcp…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 232 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: Fix memleak in nfc_llcp_send_ui_frame(). syzbot reported various memory leaks related to NFC, struct nfc_llcp_sock, sk_buff, nfc_dev, etc. [0] The leading log hinted that nfc_llcp_send_ui_frame() failed to allocate skb due to sock_error(sk) being -ENXIO. ENXIO is set by nfc_llcp_socket_release() when struct nfc_llcp_local is destroyed by local_cleanup(). The problem is that there is no synchronisation between nfc_llcp_send_ui_frame() and local_cleanup(), and skb could be put into local-&amp;gt;tx_queue after it was purged in local_cleanup():   CPU1                          CPU2   ----                          ----   nfc_llcp_send_ui_frame()      local_cleanup()   |- do {                       &amp;#39;      |- pdu = nfc_alloc_send_skb(..., &amp;amp;err)      |                          .      |                          |- nfc_llcp_socket_release(local, false, ENXIO);      |                          |- skb_queue_purge(&amp;amp;local-&amp;gt;tx_queue); |      |                          &amp;#39; |      |- skb_queue_tail(&amp;amp;local-&amp;gt;tx_queue, pdu); |     ... |      |- pdu = nfc_alloc_send_skb(..., &amp;amp;err) | ^._________________________________.&amp;#39; local_cleanup() is called for struct nfc_llcp_local only after nfc_llcp_remove_local() unlinks it from llcp_devices. If we hold local-&amp;gt;tx_queue.lock then, we can synchronise the thread and nfc_llcp_send_ui_frame(). Let&amp;#39;s do that and check list_empty(&amp;amp;local-&amp;gt;list) before queuing skb to local-&amp;gt;tx_queue in nfc_llcp…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-23150</guid>
    </item>
  </channel>
</rss>
