<?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>Fri, 20 Nov 2026 21:49:59 +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-26739</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-26739</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-26739</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0420 — 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-0420</link>
      <description>certfr-2024-avi-0420</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0420</guid>
    </item>
    <item>
      <title>OESA-2024-1617 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-1617</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.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;
x86/kvm: Disable kvmclock on all CPUs on shutdown&#13;
&#13;
Currenly, we disable kvmclock from machine_shutdown() hook and this
only happens for boot CPU. We need to disable it for all CPUs to
guard against memory corruption e.g. on restore from hibernate.&#13;
&#13;
Note, writing &amp;amp;apos;0&amp;amp;apos; to kvmclock MSR doesn&amp;amp;apos;t clear memory location, it
just prevents hypervisor from updating the location so for the short
while after write and while CPU is still alive, the clock remains usable
and correct so we don&amp;amp;apos;t need to switch to some other clocksource.(CVE-2021-47110)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
i40e: Fix NULL ptr dereference on VSI filter sync&#13;
&#13;
Remove the reason of null pointer dereference in sync VSI filters.
Added new I40E_VSI_RELEASING flag to signalize deleting and releasing
of VSI resources to sync this thread with sync filters subtask.
Without this patch it is possible to start update the VSI filter list
after VSI is removed, that&amp;amp;apos;s causing a kernel oops.(CVE-2021-47184)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
erofs: fix pcluster use-after-free on UP platforms&#13;
&#13;
During stress testing with CONFIG_SMP disabled, KASAN reports as below:&#13;
&#13;
==================================================================
BUG: KASAN: use-after-free in __mutex_lock+0xe…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.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;
x86/kvm: Disable kvmclock on all CPUs on shutdown&#13;
&#13;
Currenly, we disable kvmclock from machine_shutdown() hook and this
only happens for boot CPU. We need to disable it for all CPUs to
guard against memory corruption e.g. on restore from hibernate.&#13;
&#13;
Note, writing &amp;amp;apos;0&amp;amp;apos; to kvmclock MSR doesn&amp;amp;apos;t clear memory location, it
just prevents hypervisor from updating the location so for the short
while after write and while CPU is still alive, the clock remains usable
and correct so we don&amp;amp;apos;t need to switch to some other clocksource.(CVE-2021-47110)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
i40e: Fix NULL ptr dereference on VSI filter sync&#13;
&#13;
Remove the reason of null pointer dereference in sync VSI filters.
Added new I40E_VSI_RELEASING flag to signalize deleting and releasing
of VSI resources to sync this thread with sync filters subtask.
Without this patch it is possible to start update the VSI filter list
after VSI is removed, that&amp;amp;apos;s causing a kernel oops.(CVE-2021-47184)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
erofs: fix pcluster use-after-free on UP platforms&#13;
&#13;
During stress testing with CONFIG_SMP disabled, KASAN reports as below:&#13;
&#13;
==================================================================
BUG: KASAN: use-after-free in __mutex_lock+0xe…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-1617</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-26739</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26739</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 133 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/sched: act_mirred: don&amp;#39;t override retval if we already lost the skb If we&amp;#39;re redirecting the skb, and haven&amp;#39;t called tcf_mirred_forward(), yet, we need to tell the core to drop the skb by setting the retcode to SHOT. If we have called tcf_mirred_forward(), however, the skb is out of our hands and returning SHOT will lead to UaF. Move the retval override to the error path which actually need it.&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 133 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/sched: act_mirred: don&amp;#39;t override retval if we already lost the skb If we&amp;#39;re redirecting the skb, and haven&amp;#39;t called tcf_mirred_forward(), yet, we need to tell the core to drop the skb by setting the retcode to SHOT. If we have called tcf_mirred_forward(), however, the skb is out of our hands and returning SHOT will lead to UaF. Move the retval override to the error path which actually need it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26739</guid>
    </item>
  </channel>
</rss>
