<?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>Thu, 19 Nov 2026 17:57:09 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-49932</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-49932</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-49932</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0152 — 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-2025-avi-0152</link>
      <description>certfr-2025-avi-0152</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0152</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-49932</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-49932</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 205 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: btrfs: don&amp;#39;t readahead the relocation inode on RST On relocation we&amp;#39;re doing readahead on the relocation inode, but if the filesystem is backed by a RAID stripe tree we can get ENOENT (e.g. due to preallocated extents not being mapped in the RST) from the lookup. But readahead doesn&amp;#39;t handle the error and submits invalid reads to the device, causing an assertion in the scatter-gather list code:   BTRFS info (device nvme1n1): balance: start -d -m -s   BTRFS info (device nvme1n1): relocating block group 6480920576 flags data|raid0   BTRFS error (device nvme1n1): cannot find raid-stripe for logical [6481928192, 6481969152] devid 2, profile raid0   ------------[ cut here ]------------   kernel BUG at include/linux/scatterlist.h:115!   Oops: invalid opcode: 0000 [#1] PREEMPT SMP PTI   CPU: 0 PID: 1012 Comm: btrfs Not tainted 6.10.0-rc7+ #567   RIP: 0010:__blk_rq_map_sg+0x339/0x4a0   RSP: 0018:ffffc90001a43820 EFLAGS: 00010202   RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffea00045d4802   RDX: 0000000117520000 RSI: 0000000000000000 RDI: ffff8881027d1000   RBP: 0000000000003000 R08: ffffea00045d4902 R09: 0000000000000000   R10: 0000000000000000 R11: 0000000000001000 R12: ffff8881003d10b8   R13: ffffc90001a438f0 R14: 0000000000000000 R15: 0000000000003000   FS:  00007fcc048a6900(0000) GS:ffff88813bc00000(0000) knlGS:0000000000000000   CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033   CR2: 000000002cd11000 C…&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 205 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: btrfs: don&amp;#39;t readahead the relocation inode on RST On relocation we&amp;#39;re doing readahead on the relocation inode, but if the filesystem is backed by a RAID stripe tree we can get ENOENT (e.g. due to preallocated extents not being mapped in the RST) from the lookup. But readahead doesn&amp;#39;t handle the error and submits invalid reads to the device, causing an assertion in the scatter-gather list code:   BTRFS info (device nvme1n1): balance: start -d -m -s   BTRFS info (device nvme1n1): relocating block group 6480920576 flags data|raid0   BTRFS error (device nvme1n1): cannot find raid-stripe for logical [6481928192, 6481969152] devid 2, profile raid0   ------------[ cut here ]------------   kernel BUG at include/linux/scatterlist.h:115!   Oops: invalid opcode: 0000 [#1] PREEMPT SMP PTI   CPU: 0 PID: 1012 Comm: btrfs Not tainted 6.10.0-rc7+ #567   RIP: 0010:__blk_rq_map_sg+0x339/0x4a0   RSP: 0018:ffffc90001a43820 EFLAGS: 00010202   RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffea00045d4802   RDX: 0000000117520000 RSI: 0000000000000000 RDI: ffff8881027d1000   RBP: 0000000000003000 R08: ffffea00045d4902 R09: 0000000000000000   R10: 0000000000000000 R11: 0000000000001000 R12: ffff8881003d10b8   R13: ffffc90001a438f0 R14: 0000000000000000 R15: 0000000000003000   FS:  00007fcc048a6900(0000) GS:ffff88813bc00000(0000) knlGS:0000000000000000   CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033   CR2: 000000002cd11000 C…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-49932</guid>
    </item>
  </channel>
</rss>
