<?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 05:51:50 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-26890</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-26890</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2024-26890</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0546 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0546</link>
      <description>certfr-2024-avi-0546</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0546</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-26890</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26890</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 78 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btrtl: fix out of bounds memory access The problem is detected by KASAN. btrtl driver uses private hci data to store &amp;#39;struct btrealtek_data&amp;#39;. If btrtl driver is used with btusb, then memory for private hci data is allocated in btusb. But no private data is allocated after hci_dev, when btrtl is used with hci_h5. This commit adds memory allocation for hci_h5 case.  ==================================================================  BUG: KASAN: slab-out-of-bounds in btrtl_initialize+0x6cc/0x958 [btrtl]  Write of size 8 at addr ffff00000f5a5748 by task kworker/u9:0/76  Hardware name: Pine64 PinePhone (1.2) (DT)  Workqueue: hci0 hci_power_on [bluetooth]  Call trace:   dump_backtrace+0x9c/0x128   show_stack+0x20/0x38   dump_stack_lvl+0x48/0x60   print_report+0xf8/0x5d8   kasan_report+0x90/0xd0   __asan_store8+0x9c/0xc0   	 [btrtl]   h5_btrtl_setup+0xd0/0x2f8 [hci_uart]   h5_setup+0x50/0x80 [hci_uart]   hci_uart_setup+0xd4/0x260 [hci_uart]   hci_dev_open_sync+0x1cc/0xf68 [bluetooth]   hci_dev_do_open+0x34/0x90 [bluetooth]   hci_power_on+0xc4/0x3c8 [bluetooth]   process_one_work+0x328/0x6f0   worker_thread+0x410/0x778   kthread+0x168/0x178   ret_from_fork+0x10/0x20  Allocated by task 53:   kasan_save_stack+0x3c/0x68   kasan_save_track+0x20/0x40   kasan_save_alloc_info+0x68/0x78   __kasan_kmalloc+0xd4/0xd8   __kmalloc+0x1b4/0x3b0   hci_alloc_dev_priv+0x28/0xa58 [bluetooth]   hci_uart_register_device+0x118…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 78 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btrtl: fix out of bounds memory access The problem is detected by KASAN. btrtl driver uses private hci data to store &amp;#39;struct btrealtek_data&amp;#39;. If btrtl driver is used with btusb, then memory for private hci data is allocated in btusb. But no private data is allocated after hci_dev, when btrtl is used with hci_h5. This commit adds memory allocation for hci_h5 case.  ==================================================================  BUG: KASAN: slab-out-of-bounds in btrtl_initialize+0x6cc/0x958 [btrtl]  Write of size 8 at addr ffff00000f5a5748 by task kworker/u9:0/76  Hardware name: Pine64 PinePhone (1.2) (DT)  Workqueue: hci0 hci_power_on [bluetooth]  Call trace:   dump_backtrace+0x9c/0x128   show_stack+0x20/0x38   dump_stack_lvl+0x48/0x60   print_report+0xf8/0x5d8   kasan_report+0x90/0xd0   __asan_store8+0x9c/0xc0   	 [btrtl]   h5_btrtl_setup+0xd0/0x2f8 [hci_uart]   h5_setup+0x50/0x80 [hci_uart]   hci_uart_setup+0xd4/0x260 [hci_uart]   hci_dev_open_sync+0x1cc/0xf68 [bluetooth]   hci_dev_do_open+0x34/0x90 [bluetooth]   hci_power_on+0xc4/0x3c8 [bluetooth]   process_one_work+0x328/0x6f0   worker_thread+0x410/0x778   kthread+0x168/0x178   ret_from_fork+0x10/0x20  Allocated by task 53:   kasan_save_stack+0x3c/0x68   kasan_save_track+0x20/0x40   kasan_save_alloc_info+0x68/0x78   __kasan_kmalloc+0xd4/0xd8   __kmalloc+0x1b4/0x3b0   hci_alloc_dev_priv+0x28/0xa58 [bluetooth]   hci_uart_register_device+0x118…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26890</guid>
    </item>
  </channel>
</rss>
