<?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 12:00:47 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-27031</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-27031</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-27031</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0526 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent une élé…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0526</link>
      <description>certfr-2024-avi-0526</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0526</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-27031</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-27031</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: NFS: Fix nfs_netfs_issue_read() xarray locking for writeback interrupt The loop inside nfs_netfs_issue_read() currently does not disable interrupts while iterating through pages in the xarray to submit for NFS read.  This is not safe though since after taking xa_lock, another page in the mapping could be processed for writeback inside an interrupt, and deadlock can occur.  The fix is simple and clean if we use xa_for_each_range(), which handles the iteration with RCU while reducing code complexity. The problem is easily reproduced with the following test:  mount -o vers=3,fsc 127.0.0.1:/export /mnt/nfs  dd if=/dev/zero of=/mnt/nfs/file1.bin bs=4096 count=1  echo 3 &amp;gt; /proc/sys/vm/drop_caches  dd if=/mnt/nfs/file1.bin of=/dev/null  umount /mnt/nfs On the console with a lockdep-enabled kernel a message similar to the following will be seen:  ================================  WARNING: inconsistent lock state  6.7.0-lockdbg+ #10 Not tainted  --------------------------------  inconsistent {IN-SOFTIRQ-W} -&amp;gt; {SOFTIRQ-ON-W} usage.  test5/1708 [HC0[0]:SC0[0]:HE1:SE1] takes:  ffff888127baa598 (&amp;amp;xa-&amp;gt;xa_lock#4){+.?.}-{3:3}, at: nfs_netfs_issue_read+0x1b2/0x4b0 [nfs]  {IN-SOFTIRQ-W} state was registered at:    lock_acquire+0x144/0x380    _raw_spin_lock_irqsave+0x4e/0xa0    __folio_end_writeback+0x17e/0x5c0    folio_end_writeback+0x93/0x1b0    iomap_finish_ioend+0xeb/0x6a0    blk_update_request+0x204/0x7f0    blk_mq_end_re…&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: NFS: Fix nfs_netfs_issue_read() xarray locking for writeback interrupt The loop inside nfs_netfs_issue_read() currently does not disable interrupts while iterating through pages in the xarray to submit for NFS read.  This is not safe though since after taking xa_lock, another page in the mapping could be processed for writeback inside an interrupt, and deadlock can occur.  The fix is simple and clean if we use xa_for_each_range(), which handles the iteration with RCU while reducing code complexity. The problem is easily reproduced with the following test:  mount -o vers=3,fsc 127.0.0.1:/export /mnt/nfs  dd if=/dev/zero of=/mnt/nfs/file1.bin bs=4096 count=1  echo 3 &amp;gt; /proc/sys/vm/drop_caches  dd if=/mnt/nfs/file1.bin of=/dev/null  umount /mnt/nfs On the console with a lockdep-enabled kernel a message similar to the following will be seen:  ================================  WARNING: inconsistent lock state  6.7.0-lockdbg+ #10 Not tainted  --------------------------------  inconsistent {IN-SOFTIRQ-W} -&amp;gt; {SOFTIRQ-ON-W} usage.  test5/1708 [HC0[0]:SC0[0]:HE1:SE1] takes:  ffff888127baa598 (&amp;amp;xa-&amp;gt;xa_lock#4){+.?.}-{3:3}, at: nfs_netfs_issue_read+0x1b2/0x4b0 [nfs]  {IN-SOFTIRQ-W} state was registered at:    lock_acquire+0x144/0x380    _raw_spin_lock_irqsave+0x4e/0xa0    __folio_end_writeback+0x17e/0x5c0    folio_end_writeback+0x93/0x1b0    iomap_finish_ioend+0xeb/0x6a0    blk_update_request+0x204/0x7f0    blk_mq_end_re…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-27031</guid>
    </item>
  </channel>
</rss>
