<?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 03:47:53 +0000</lastBuildDate>
    <item>
      <title>ALSA-2024:6567 — Moderate: kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2024:6567</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: bpftool, AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core and 52 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: efivarfs: force RO when remounting if SetVariable is not supported (CVE-2023-52463)
  * kernel: nfsd: fix RELEASE_LOCKOWNER (CVE-2024-26629)
  * kernel: mm: cachestat: fix folio read-after-free in cache walk (CVE-2024-26630)
  * kernel: mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again (CVE-2024-26720)
  * kernel: Bluetooth: af_bluetooth: Fix deadlock (CVE-2024-26886)
  * kernel: kprobes/x86: Use copy_from_kernel_nofault() to read from unsafe address (CVE-2024-26946)
  * kernel: KVM: SVM: Flush pages under kvm-&amp;amp;gt;lock to fix UAF in svm_register_enc_region() (CVE-2024-35791)
  * kernel: mm: cachestat: fix two shmem bugs (CVE-2024-35797)
  * kernel: x86/coco: Require seeding RNG with RDRAND on CoCo systems (CVE-2024-35875)
  * kernel: mm/hugetlb: fix missing hugetlb_lock for resv uncharge (CVE-2024-36000)
  * kernel: iommufd: Fix missing update of domains_itree after splitting iopt_area (CVE-2023-52801)
  * kernel: net: fix out-of-bounds access in ops_init (CVE-2024-36883)
  * kernel: regmap: maple: Fix cache corruption in regcache_maple_drop() (CVE-2024-36019)
  * kernel: usb-storage: alauda: Check whether the media is initialized (CVE-2024-38619)
  * kernel: net: bridge: mst: fix vlan use-after-free (CVE-2024-36979)
  * kernel: scsi: qedf: Ensure the copied buf is NUL terminated (CVE-2024-38559)
  * kernel: xhci: Handle TD clearing fo…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: bpftool, AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core and 52 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: efivarfs: force RO when remounting if SetVariable is not supported (CVE-2023-52463)
  * kernel: nfsd: fix RELEASE_LOCKOWNER (CVE-2024-26629)
  * kernel: mm: cachestat: fix folio read-after-free in cache walk (CVE-2024-26630)
  * kernel: mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again (CVE-2024-26720)
  * kernel: Bluetooth: af_bluetooth: Fix deadlock (CVE-2024-26886)
  * kernel: kprobes/x86: Use copy_from_kernel_nofault() to read from unsafe address (CVE-2024-26946)
  * kernel: KVM: SVM: Flush pages under kvm-&amp;amp;gt;lock to fix UAF in svm_register_enc_region() (CVE-2024-35791)
  * kernel: mm: cachestat: fix two shmem bugs (CVE-2024-35797)
  * kernel: x86/coco: Require seeding RNG with RDRAND on CoCo systems (CVE-2024-35875)
  * kernel: mm/hugetlb: fix missing hugetlb_lock for resv uncharge (CVE-2024-36000)
  * kernel: iommufd: Fix missing update of domains_itree after splitting iopt_area (CVE-2023-52801)
  * kernel: net: fix out-of-bounds access in ops_init (CVE-2024-36883)
  * kernel: regmap: maple: Fix cache corruption in regcache_maple_drop() (CVE-2024-36019)
  * kernel: usb-storage: alauda: Check whether the media is initialized (CVE-2024-38619)
  * kernel: net: bridge: mst: fix vlan use-after-free (CVE-2024-36979)
  * kernel: scsi: qedf: Ensure the copied buf is NUL terminated (CVE-2024-38559)
  * kernel: xhci: Handle TD clearing fo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2024:6567</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-42102</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-42102</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-2024-42102</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0719 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0719</link>
      <description>certfr-2024-avi-0719</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0719</guid>
    </item>
    <item>
      <title>OESA-2024-1992 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-1992</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
USB: core: Make do_proc_control() and do_proc_bulk() killable&#13;
&#13;
The USBDEVFS_CONTROL and USBDEVFS_BULK ioctls invoke
usb_start_wait_urb(), which contains an uninterruptible wait with a
user-specified timeout value.  If timeout value is very large and the
device being accessed does not respond in a reasonable amount of time,
the kernel will complain about &amp;amp;quot;Task X blocked for more than N
seconds&amp;amp;quot;, as found in testing by syzbot:&#13;
&#13;
INFO: task syz-executor.0:8700 blocked for more than 143 seconds.
      Not tainted 5.14.0-rc7-syzkaller #0
&amp;amp;quot;echo 0 &amp;amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;amp;quot; disables this message.
task:syz-executor.0  state:D stack:23192 pid: 8700 ppid:  8455 flags:0x00004004
Call Trace:
 context_switch kernel/sched/core.c:4681 [inline]
 __schedule+0xc07/0x11f0 kernel/sched/core.c:5938
 schedule+0x14b/0x210 kernel/sched/core.c:6017
 schedule_timeout+0x98/0x2f0 kernel/time/timer.c:1857
 do_wait_for_common+0x2da/0x480 kernel/sched/completion.c:85
 __wait_for_common kernel/sched/completion.c:106 [inline]
 wait_for_common kernel/sched/completion.c:117 [inline]
 wait_for_completion_timeout+0x46/0x60 kernel/sched/completion.c:157
 usb_start_wait_urb+0x167/0x550 drivers/usb/core/message.c:63
 do_proc_bulk+0x978/0x1080 drivers/usb/core/devio.c:1236
 proc_bulk drivers/usb/core/devio.c:1273 [inline]
 usbdev…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
USB: core: Make do_proc_control() and do_proc_bulk() killable&#13;
&#13;
The USBDEVFS_CONTROL and USBDEVFS_BULK ioctls invoke
usb_start_wait_urb(), which contains an uninterruptible wait with a
user-specified timeout value.  If timeout value is very large and the
device being accessed does not respond in a reasonable amount of time,
the kernel will complain about &amp;amp;quot;Task X blocked for more than N
seconds&amp;amp;quot;, as found in testing by syzbot:&#13;
&#13;
INFO: task syz-executor.0:8700 blocked for more than 143 seconds.
      Not tainted 5.14.0-rc7-syzkaller #0
&amp;amp;quot;echo 0 &amp;amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;amp;quot; disables this message.
task:syz-executor.0  state:D stack:23192 pid: 8700 ppid:  8455 flags:0x00004004
Call Trace:
 context_switch kernel/sched/core.c:4681 [inline]
 __schedule+0xc07/0x11f0 kernel/sched/core.c:5938
 schedule+0x14b/0x210 kernel/sched/core.c:6017
 schedule_timeout+0x98/0x2f0 kernel/time/timer.c:1857
 do_wait_for_common+0x2da/0x480 kernel/sched/completion.c:85
 __wait_for_common kernel/sched/completion.c:106 [inline]
 wait_for_common kernel/sched/completion.c:117 [inline]
 wait_for_completion_timeout+0x46/0x60 kernel/sched/completion.c:157
 usb_start_wait_urb+0x167/0x550 drivers/usb/core/message.c:63
 do_proc_bulk+0x978/0x1080 drivers/usb/core/devio.c:1236
 proc_bulk drivers/usb/core/devio.c:1273 [inline]
 usbdev…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-1992</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-42102</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-42102</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 172 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Revert &amp;#34;mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again&amp;#34; Patch series &amp;#34;mm: Avoid possible overflows in dirty throttling&amp;#34;. Dirty throttling logic assumes dirty limits in page units fit into 32-bits.  This patch series makes sure this is true (see patch 2/2 for more details). This patch (of 2): This reverts commit 9319b647902cbd5cc884ac08a8a6d54ce111fc78. The commit is broken in several ways.  Firstly, the removed (u64) cast from the multiplication will introduce a multiplication overflow on 32-bit archs if wb_thresh * bg_thresh &amp;gt;= 1&amp;lt;&amp;lt;32 (which is actually common - the default settings with 4GB of RAM will trigger this).  Secondly, the div64_u64() is unnecessarily expensive on 32-bit archs.  We have div64_ul() in case we want to be safe &amp;amp; cheap.  Thirdly, if dirty thresholds are larger than 1&amp;lt;&amp;lt;32 pages, then dirty balancing is going to blow up in many other spectacular ways anyway so trying to fix one possible overflow is just moot.&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 172 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Revert &amp;#34;mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again&amp;#34; Patch series &amp;#34;mm: Avoid possible overflows in dirty throttling&amp;#34;. Dirty throttling logic assumes dirty limits in page units fit into 32-bits.  This patch series makes sure this is true (see patch 2/2 for more details). This patch (of 2): This reverts commit 9319b647902cbd5cc884ac08a8a6d54ce111fc78. The commit is broken in several ways.  Firstly, the removed (u64) cast from the multiplication will introduce a multiplication overflow on 32-bit archs if wb_thresh * bg_thresh &amp;gt;= 1&amp;lt;&amp;lt;32 (which is actually common - the default settings with 4GB of RAM will trigger this).  Secondly, the div64_u64() is unnecessarily expensive on 32-bit archs.  We have div64_ul() in case we want to be safe &amp;amp; cheap.  Thirdly, if dirty thresholds are larger than 1&amp;lt;&amp;lt;32 pages, then dirty balancing is going to blow up in many other spectacular ways anyway so trying to fix one possible overflow is just moot.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-42102</guid>
    </item>
  </channel>
</rss>
