<?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 07:06:14 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98739</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-98739</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-98739</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1375 — 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-1375</link>
      <description>certfr-2026-avi-1375</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1375</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98739</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-98739</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: Fix initial port reference race For RFCOMM_RELEASE_ONHUP devices, rfcomm_tty_install() and __rfcomm_release_dev() both use RFCOMM_TTY_OWNED to decide who drops the initial tty_port reference. The release path tests the bit separately from the install path setting it, so both can drop that reference. The synchronous hangup does not prevent this race: port-&amp;gt;tty is not assigned until tty_port_open(), after installation. The following interleaving is possible:   1. Install and release each obtain a reference with rfcomm_dev_get().   2. Release observes RFCOMM_TTY_OWNED clear.   3. Install sets RFCOMM_TTY_OWNED and drops the initial reference.   4. Release drops the same initial reference again.   5. TTY cleanup drops its reference and frees the device.   6. Release performs its final tty_port_put() on the freed port. KASAN reported:   BUG: KASAN: slab-use-after-free in tty_port_put+0x22/0x190   Write of size 4 at addr ffff8881001d3d5c by task poc/92   Call Trace:    tty_port_put+0x22/0x190    rfcomm_dev_ioctl+0x1d4/0x1930    sock_do_ioctl+0x110/0x260    sock_ioctl+0x380/0x590    __x64_sys_ioctl+0x134/0x1c0   Allocated by task 88:    rfcomm_dev_ioctl+0x8f6/0x1930    sock_do_ioctl+0x110/0x260    sock_ioctl+0x380/0x590    __x64_sys_ioctl+0x134/0x1c0   Freed by task 65:    kfree+0x131/0x3c0    rfcomm_dev_destruct+0x23b/0x2f0    release_one_tty+0xc1/0x370    process_one_work+0x661/0x1090 Use test_a…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: Fix initial port reference race For RFCOMM_RELEASE_ONHUP devices, rfcomm_tty_install() and __rfcomm_release_dev() both use RFCOMM_TTY_OWNED to decide who drops the initial tty_port reference. The release path tests the bit separately from the install path setting it, so both can drop that reference. The synchronous hangup does not prevent this race: port-&amp;gt;tty is not assigned until tty_port_open(), after installation. The following interleaving is possible:   1. Install and release each obtain a reference with rfcomm_dev_get().   2. Release observes RFCOMM_TTY_OWNED clear.   3. Install sets RFCOMM_TTY_OWNED and drops the initial reference.   4. Release drops the same initial reference again.   5. TTY cleanup drops its reference and frees the device.   6. Release performs its final tty_port_put() on the freed port. KASAN reported:   BUG: KASAN: slab-use-after-free in tty_port_put+0x22/0x190   Write of size 4 at addr ffff8881001d3d5c by task poc/92   Call Trace:    tty_port_put+0x22/0x190    rfcomm_dev_ioctl+0x1d4/0x1930    sock_do_ioctl+0x110/0x260    sock_ioctl+0x380/0x590    __x64_sys_ioctl+0x134/0x1c0   Allocated by task 88:    rfcomm_dev_ioctl+0x8f6/0x1930    sock_do_ioctl+0x110/0x260    sock_ioctl+0x380/0x590    __x64_sys_ioctl+0x134/0x1c0   Freed by task 65:    kfree+0x131/0x3c0    rfcomm_dev_destruct+0x23b/0x2f0    release_one_tty+0xc1/0x370    process_one_work+0x661/0x1090 Use test_a…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-98739</guid>
    </item>
  </channel>
</rss>
