<?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:59:16 +0000</lastBuildDate>
    <item>
      <title>ALSA-2024:4928 — Moderate: kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2024:4928</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: block: null pointer dereference in ioctl.c when length and logical block size are misaligned (CVE-2023-52458)
  * kernel: ext4: avoid allocating blocks from corrupted group in ext4_mb_try_best_found() (CVE-2024-26773)
  * kernel: bpf: Fix racing between bpf_timer_cancel_and_free and bpf_timer_cancel (CVE-2024-26737)
  * kernel: dm: call the resume method on internal suspend (CVE-2024-26880)
  * kernel: net/ipv6: avoid possible UAF in ip6_route_mpath_notify() (CVE-2024-26852)
  * kernel: Squashfs: check the inode number is not the invalid value of zero (CVE-2024-26982)
  * kernel: nfp: flower: handle acti_netdevs allocation failure (CVE-2024-27046)
  * kernel: octeontx2-af: Use separate handlers for interrupts (CVE-2024-27030)
  * kernel: icmp: prevent possible NULL dereferences from icmp_build_probe() (CVE-2024-35857)
  * kernel: mlxbf_gige: call request_irq() after NAPI initialized (CVE-2024-35907)
  * kernel: mlxbf_gige: stop interface during shutdown (CVE-2024-35885)
  * kernel: scsi: libfc: Fix potential NULL pointer dereference in fc_lport_ptp_setup() (CVE-2023-52809)
  * kernel: can: j1939: j1939_netdev_start(): fix UAF for rx_kref of j1939_priv (CVE-2021-47459)
  * kernel: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (CVE-2024-36924)
  * kernel: scsi: lpfc: Move NPIV&amp;#39;s transport unregistration to after resource clean up (CVE-202…&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: block: null pointer dereference in ioctl.c when length and logical block size are misaligned (CVE-2023-52458)
  * kernel: ext4: avoid allocating blocks from corrupted group in ext4_mb_try_best_found() (CVE-2024-26773)
  * kernel: bpf: Fix racing between bpf_timer_cancel_and_free and bpf_timer_cancel (CVE-2024-26737)
  * kernel: dm: call the resume method on internal suspend (CVE-2024-26880)
  * kernel: net/ipv6: avoid possible UAF in ip6_route_mpath_notify() (CVE-2024-26852)
  * kernel: Squashfs: check the inode number is not the invalid value of zero (CVE-2024-26982)
  * kernel: nfp: flower: handle acti_netdevs allocation failure (CVE-2024-27046)
  * kernel: octeontx2-af: Use separate handlers for interrupts (CVE-2024-27030)
  * kernel: icmp: prevent possible NULL dereferences from icmp_build_probe() (CVE-2024-35857)
  * kernel: mlxbf_gige: call request_irq() after NAPI initialized (CVE-2024-35907)
  * kernel: mlxbf_gige: stop interface during shutdown (CVE-2024-35885)
  * kernel: scsi: libfc: Fix potential NULL pointer dereference in fc_lport_ptp_setup() (CVE-2023-52809)
  * kernel: can: j1939: j1939_netdev_start(): fix UAF for rx_kref of j1939_priv (CVE-2021-47459)
  * kernel: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (CVE-2024-36924)
  * kernel: scsi: lpfc: Move NPIV&amp;#39;s transport unregistration to after resource clean up (CVE-202…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2024:4928</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-26737</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-26737</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-26737</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0334 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;le noyau Linux de Debian&lt;/span&gt;. Elles permet…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0334</link>
      <description>certfr-2024-avi-0334</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0334</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-26737</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26737</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 104 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Fix racing between bpf_timer_cancel_and_free and bpf_timer_cancel The following race is possible between bpf_timer_cancel_and_free and bpf_timer_cancel. It will lead a UAF on the timer-&amp;gt;timer. bpf_timer_cancel(); 	spin_lock(); 	t = timer-&amp;gt;time; 	spin_unlock(); 					bpf_timer_cancel_and_free(); 						spin_lock(); 						t = timer-&amp;gt;timer; 						timer-&amp;gt;timer = NULL; 						spin_unlock(); 						hrtimer_cancel(&amp;amp;t-&amp;gt;timer); 						kfree(t); 	/* UAF on t */ 	hrtimer_cancel(&amp;amp;t-&amp;gt;timer); In bpf_timer_cancel_and_free, this patch frees the timer-&amp;gt;timer after a rcu grace period. This requires a rcu_head addition to the &amp;#34;struct bpf_hrtimer&amp;#34;. Another kfree(t) happens in bpf_timer_init, this does not need a kfree_rcu because it is still under the spin_lock and timer-&amp;gt;timer has not been visible by others yet. In bpf_timer_cancel, rcu_read_lock() is added because this helper can be used in a non rcu critical section context (e.g. from a sleepable bpf prog). Other timer-&amp;gt;timer usages in helpers.c have been audited, bpf_timer_cancel() is the only place where timer-&amp;gt;timer is used outside of the spin_lock. Another solution considered is to mark a t-&amp;gt;flag in bpf_timer_cancel and clear it after hrtimer_cancel() is done.  In bpf_timer_cancel_and_free, it busy waits for the flag to be cleared before kfree(t). This patch goes with a straight forward solution and frees timer-&amp;gt;timer after a rcu grace period.&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 104 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Fix racing between bpf_timer_cancel_and_free and bpf_timer_cancel The following race is possible between bpf_timer_cancel_and_free and bpf_timer_cancel. It will lead a UAF on the timer-&amp;gt;timer. bpf_timer_cancel(); 	spin_lock(); 	t = timer-&amp;gt;time; 	spin_unlock(); 					bpf_timer_cancel_and_free(); 						spin_lock(); 						t = timer-&amp;gt;timer; 						timer-&amp;gt;timer = NULL; 						spin_unlock(); 						hrtimer_cancel(&amp;amp;t-&amp;gt;timer); 						kfree(t); 	/* UAF on t */ 	hrtimer_cancel(&amp;amp;t-&amp;gt;timer); In bpf_timer_cancel_and_free, this patch frees the timer-&amp;gt;timer after a rcu grace period. This requires a rcu_head addition to the &amp;#34;struct bpf_hrtimer&amp;#34;. Another kfree(t) happens in bpf_timer_init, this does not need a kfree_rcu because it is still under the spin_lock and timer-&amp;gt;timer has not been visible by others yet. In bpf_timer_cancel, rcu_read_lock() is added because this helper can be used in a non rcu critical section context (e.g. from a sleepable bpf prog). Other timer-&amp;gt;timer usages in helpers.c have been audited, bpf_timer_cancel() is the only place where timer-&amp;gt;timer is used outside of the spin_lock. Another solution considered is to mark a t-&amp;gt;flag in bpf_timer_cancel and clear it after hrtimer_cancel() is done.  In bpf_timer_cancel_and_free, it busy waits for the flag to be cleared before kfree(t). This patch goes with a straight forward solution and frees timer-&amp;gt;timer after a rcu grace period.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26737</guid>
    </item>
  </channel>
</rss>
