<?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 19:37:25 +0000</lastBuildDate>
    <item>
      <title>ALSA-2024:6997 — Important: kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2024:6997</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: uio: Fix use-after-free in uio_open (CVE-2023-52439)
  * kernel: net/sched: act_mirred: don&amp;#39;t override retval if we already lost the skb (CVE-2024-26739)
  * kernel: ARM: 9359/1: flush: check if the folio is reserved for no-mapping addresses (CVE-2024-26947)
  * kernel: scsi: qla2xxx: Fix command flush on cable pull (CVE-2024-26931)
  * kernel: scsi: qla2xxx: Fix double free of the ha-&amp;amp;gt;vp_map pointer (CVE-2024-26930)
  * kernel: scsi: qla2xxx: Fix double free of fcport (CVE-2024-26929)
  * kernel: fork: defer linking file vma until vma is fully initialized (CVE-2024-27022)
  * kernel: KVM: x86/mmu: x86: Don&amp;amp;#39;t overflow lpage_info when checking attributes (CVE-2024-26991)
  * kernel: bpf, sockmap: Prevent lock inversion deadlock in map delete elem (CVE-2024-35895)
  * kernel: tty: n_gsm: fix possible out-of-bounds in gsm0_receive() (CVE-2024-36016)
  * kernel: gpiolib: cdev: Fix use after free in lineinfo_changed_notify (CVE-2024-36899)
  * kernel: cpufreq: exit() callback is optional (CVE-2024-38615)
  * kernel: ring-buffer: Fix a race between readers and resize checks (CVE-2024-38601)
  * kernel: cppc_cpufreq: Fix possible null pointer dereference (CVE-2024-38573)
  * kernel: gfs2: Fix potential glock use-after-free on unmount (CVE-2024-38570)
  * kernel: wifi: nl80211: Avoid address calculations via out of bounds array indexing (CVE-2024-38562)…&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: uio: Fix use-after-free in uio_open (CVE-2023-52439)
  * kernel: net/sched: act_mirred: don&amp;#39;t override retval if we already lost the skb (CVE-2024-26739)
  * kernel: ARM: 9359/1: flush: check if the folio is reserved for no-mapping addresses (CVE-2024-26947)
  * kernel: scsi: qla2xxx: Fix command flush on cable pull (CVE-2024-26931)
  * kernel: scsi: qla2xxx: Fix double free of the ha-&amp;amp;gt;vp_map pointer (CVE-2024-26930)
  * kernel: scsi: qla2xxx: Fix double free of fcport (CVE-2024-26929)
  * kernel: fork: defer linking file vma until vma is fully initialized (CVE-2024-27022)
  * kernel: KVM: x86/mmu: x86: Don&amp;amp;#39;t overflow lpage_info when checking attributes (CVE-2024-26991)
  * kernel: bpf, sockmap: Prevent lock inversion deadlock in map delete elem (CVE-2024-35895)
  * kernel: tty: n_gsm: fix possible out-of-bounds in gsm0_receive() (CVE-2024-36016)
  * kernel: gpiolib: cdev: Fix use after free in lineinfo_changed_notify (CVE-2024-36899)
  * kernel: cpufreq: exit() callback is optional (CVE-2024-38615)
  * kernel: ring-buffer: Fix a race between readers and resize checks (CVE-2024-38601)
  * kernel: cppc_cpufreq: Fix possible null pointer dereference (CVE-2024-38573)
  * kernel: gfs2: Fix potential glock use-after-free on unmount (CVE-2024-38570)
  * kernel: wifi: nl80211: Avoid address calculations via out of bounds array indexing (CVE-2024-38562)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2024:6997</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-36899</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-36899</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-36899</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0578 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0578</link>
      <description>certfr-2024-avi-0578</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0578</guid>
    </item>
    <item>
      <title>OESA-2024-1706 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-1706</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;
net/mlx5e: Fix use-after-free of encap entry in neigh update handler&#13;
&#13;
Function mlx5e_rep_neigh_update() wasn&amp;amp;apos;t updated to accommodate rtnl lock
removal from TC filter update path and properly handle concurrent encap
entry insertion/deletion which can lead to following use-after-free:&#13;
&#13;
 [23827.464923] ==================================================================
 [23827.469446] BUG: KASAN: use-after-free in mlx5e_encap_take+0x72/0x140 [mlx5_core]
 [23827.470971] Read of size 4 at addr ffff8881d132228c by task kworker/u20:6/21635
 [23827.472251]
 [23827.472615] CPU: 9 PID: 21635 Comm: kworker/u20:6 Not tainted 5.13.0-rc3+ #5
 [23827.473788] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014
 [23827.475639] Workqueue: mlx5e mlx5e_rep_neigh_update [mlx5_core]
 [23827.476731] Call Trace:
 [23827.477260]  dump_stack+0xbb/0x107
 [23827.477906]  print_address_description.constprop.0+0x18/0x140
 [23827.478896]  ? mlx5e_encap_take+0x72/0x140 [mlx5_core]
 [23827.479879]  ? mlx5e_encap_take+0x72/0x140 [mlx5_core]
 [23827.480905]  kasan_report.cold+0x7c/0xd8
 [23827.481701]  ? mlx5e_encap_take+0x72/0x140 [mlx5_core]
 [23827.482744]  kasan_check_range+0x145/0x1a0
 [23827.493112]  mlx5e_encap_take+0x72/0x140 [mlx5_core]
 [23827.494054]  ? mlx5e_tc_tun_encap_info_equal_ge…&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;
net/mlx5e: Fix use-after-free of encap entry in neigh update handler&#13;
&#13;
Function mlx5e_rep_neigh_update() wasn&amp;amp;apos;t updated to accommodate rtnl lock
removal from TC filter update path and properly handle concurrent encap
entry insertion/deletion which can lead to following use-after-free:&#13;
&#13;
 [23827.464923] ==================================================================
 [23827.469446] BUG: KASAN: use-after-free in mlx5e_encap_take+0x72/0x140 [mlx5_core]
 [23827.470971] Read of size 4 at addr ffff8881d132228c by task kworker/u20:6/21635
 [23827.472251]
 [23827.472615] CPU: 9 PID: 21635 Comm: kworker/u20:6 Not tainted 5.13.0-rc3+ #5
 [23827.473788] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014
 [23827.475639] Workqueue: mlx5e mlx5e_rep_neigh_update [mlx5_core]
 [23827.476731] Call Trace:
 [23827.477260]  dump_stack+0xbb/0x107
 [23827.477906]  print_address_description.constprop.0+0x18/0x140
 [23827.478896]  ? mlx5e_encap_take+0x72/0x140 [mlx5_core]
 [23827.479879]  ? mlx5e_encap_take+0x72/0x140 [mlx5_core]
 [23827.480905]  kasan_report.cold+0x7c/0xd8
 [23827.481701]  ? mlx5e_encap_take+0x72/0x140 [mlx5_core]
 [23827.482744]  kasan_check_range+0x145/0x1a0
 [23827.493112]  mlx5e_encap_take+0x72/0x140 [mlx5_core]
 [23827.494054]  ? mlx5e_tc_tun_encap_info_equal_ge…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-1706</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-36899</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-36899</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 129 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: gpiolib: cdev: Fix use after free in lineinfo_changed_notify The use-after-free issue occurs as follows: when the GPIO chip device file is being closed by invoking gpio_chrdev_release(), watched_lines is freed by bitmap_free(), but the unregistration of lineinfo_changed_nb notifier chain failed due to waiting write rwsem. Additionally, one of the GPIO chip&amp;#39;s lines is also in the release process and holds the notifier chain&amp;#39;s read rwsem. Consequently, a race condition leads to the use-after-free of watched_lines. Here is the typical stack when issue happened: [free] gpio_chrdev_release()   --&amp;gt; bitmap_free(cdev-&amp;gt;watched_lines)                  &amp;lt;-- freed   --&amp;gt; blocking_notifier_chain_unregister()     --&amp;gt; down_write(&amp;amp;nh-&amp;gt;rwsem)                          &amp;lt;-- waiting rwsem           --&amp;gt; __down_write_common()             --&amp;gt; rwsem_down_write_slowpath()                   --&amp;gt; schedule_preempt_disabled()                     --&amp;gt; schedule() [use] st54spi_gpio_dev_release()   --&amp;gt; gpio_free()     --&amp;gt; gpiod_free()       --&amp;gt; gpiod_free_commit()         --&amp;gt; gpiod_line_state_notify()           --&amp;gt; blocking_notifier_call_chain()             --&amp;gt; down_read(&amp;amp;nh-&amp;gt;rwsem);                  &amp;lt;-- held rwsem             --&amp;gt; notifier_call_chain()               --&amp;gt; lineinfo_changed_notify()                 --&amp;gt; test_bit(xxxx, cdev-&amp;gt;watched_lines) &amp;lt;-- use after free The side effect of the use-after-free issue is that a GPIO line event is bei…&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 129 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: gpiolib: cdev: Fix use after free in lineinfo_changed_notify The use-after-free issue occurs as follows: when the GPIO chip device file is being closed by invoking gpio_chrdev_release(), watched_lines is freed by bitmap_free(), but the unregistration of lineinfo_changed_nb notifier chain failed due to waiting write rwsem. Additionally, one of the GPIO chip&amp;#39;s lines is also in the release process and holds the notifier chain&amp;#39;s read rwsem. Consequently, a race condition leads to the use-after-free of watched_lines. Here is the typical stack when issue happened: [free] gpio_chrdev_release()   --&amp;gt; bitmap_free(cdev-&amp;gt;watched_lines)                  &amp;lt;-- freed   --&amp;gt; blocking_notifier_chain_unregister()     --&amp;gt; down_write(&amp;amp;nh-&amp;gt;rwsem)                          &amp;lt;-- waiting rwsem           --&amp;gt; __down_write_common()             --&amp;gt; rwsem_down_write_slowpath()                   --&amp;gt; schedule_preempt_disabled()                     --&amp;gt; schedule() [use] st54spi_gpio_dev_release()   --&amp;gt; gpio_free()     --&amp;gt; gpiod_free()       --&amp;gt; gpiod_free_commit()         --&amp;gt; gpiod_line_state_notify()           --&amp;gt; blocking_notifier_call_chain()             --&amp;gt; down_read(&amp;amp;nh-&amp;gt;rwsem);                  &amp;lt;-- held rwsem             --&amp;gt; notifier_call_chain()               --&amp;gt; lineinfo_changed_notify()                 --&amp;gt; test_bit(xxxx, cdev-&amp;gt;watched_lines) &amp;lt;-- use after free The side effect of the use-after-free issue is that a GPIO line event is bei…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-36899</guid>
    </item>
  </channel>
</rss>
