<?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 15:24:45 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-80795</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-80795</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-80795</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1163 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1163</link>
      <description>certfr-2026-avi-1163</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1163</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-80795</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-80795</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 248 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nfc: nci: fix out-of-bounds write in nci_target_auto_activated() nci_target_auto_activated() appends a target to the fixed-size array ndev-&amp;gt;targets[NCI_MAX_DISCOVERED_TARGETS] and increments ndev-&amp;gt;n_targets without first checking the array is full; unlike its sibling nci_add_new_target(), which bails out when n_targets already equals NCI_MAX_DISCOVERED_TARGETS. ndev-&amp;gt;n_targets is only cleared by nci_clear_target_list(), so an NFCC that repeatedly re-runs discovery (RF_DISCOVER_RSP, which re-enters NCI_DISCOVERY without clearing the target list) and reports an auto-activated target (RF_INTF_ACTIVATED_NTF) drives n_targets past the limit. The append then writes a struct nfc_target past the end of the array (a slab out-of-bounds write), and nfc_targets_found() goes on to walk the array with the inflated count:   BUG: KASAN: slab-out-of-bounds in nci_add_new_protocol+0x94/0x2ac [nci]   Write of size 2 at addr ffff0000c7299a18 by task kworker/u8:0/12   Workqueue: nfc0_nci_rx_wq nci_rx_work [nci]   Call trace:    nci_add_new_protocol+0x94/0x2ac [nci]    nci_ntf_packet+0xddc/0x11a0 [nci]    nci_rx_work+0x15c/0x1e0 [nci]    process_one_work+0x2dc/0x500    worker_thread+0x240/0x460    kthread+0x1c0/0x1d0    ret_from_fork+0x10/0x20   The buggy address belongs to the cache kmalloc-2k of size 2048   The buggy address is located 1024 bytes to the right of   allocated 1560-byte region [ffff0000c7299000, ffff0000c7299618)…&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 248 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nfc: nci: fix out-of-bounds write in nci_target_auto_activated() nci_target_auto_activated() appends a target to the fixed-size array ndev-&amp;gt;targets[NCI_MAX_DISCOVERED_TARGETS] and increments ndev-&amp;gt;n_targets without first checking the array is full; unlike its sibling nci_add_new_target(), which bails out when n_targets already equals NCI_MAX_DISCOVERED_TARGETS. ndev-&amp;gt;n_targets is only cleared by nci_clear_target_list(), so an NFCC that repeatedly re-runs discovery (RF_DISCOVER_RSP, which re-enters NCI_DISCOVERY without clearing the target list) and reports an auto-activated target (RF_INTF_ACTIVATED_NTF) drives n_targets past the limit. The append then writes a struct nfc_target past the end of the array (a slab out-of-bounds write), and nfc_targets_found() goes on to walk the array with the inflated count:   BUG: KASAN: slab-out-of-bounds in nci_add_new_protocol+0x94/0x2ac [nci]   Write of size 2 at addr ffff0000c7299a18 by task kworker/u8:0/12   Workqueue: nfc0_nci_rx_wq nci_rx_work [nci]   Call trace:    nci_add_new_protocol+0x94/0x2ac [nci]    nci_ntf_packet+0xddc/0x11a0 [nci]    nci_rx_work+0x15c/0x1e0 [nci]    process_one_work+0x2dc/0x500    worker_thread+0x240/0x460    kthread+0x1c0/0x1d0    ret_from_fork+0x10/0x20   The buggy address belongs to the cache kmalloc-2k of size 2048   The buggy address is located 1024 bytes to the right of   allocated 1560-byte region [ffff0000c7299000, ffff0000c7299618)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-80795</guid>
    </item>
  </channel>
</rss>
