<?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 02:21:25 +0000</lastBuildDate>
    <item>
      <title>ALSA-2024:5363 — Important: kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2024:5363</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.  
Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: phy: (CVE-2024-26600)
  * kernel: netfilter: multiple flaws (CVE-2024-26808, CVE-2024-27065, CVE-2024-35899, CVE-2024-36005)
  * kernel: cifs: (CVE-2024-26828)
  * kernel: wifi: multiple flaws (CVE-2024-26897, CVE-2024-27052, CVE-2024-27049, CVE-2023-52651, CVE-2024-35789, CVE-2024-27434, CVE-2024-35845, CVE-2024-35937, CVE-2024-36941, CVE-2024-36922, CVE-2024-36921, CVE-2024-38575)
  * kernel: nfs: (CVE-2024-26868)
  * kernel: igc: (CVE-2024-26853)
  * kernel: dmaengine/idxd: (CVE-2024-21823)
  * kernel: ipv6: multiple flaws (CVE-2024-27417, CVE-2024-35969, CVE-2024-36903, CVE-2024-40961)
  * kernel: vt: (CVE-2024-35823)
  * kernel: efi: (CVE-2024-35800)
  * kernel: mlxsw: (CVE-2024-35852)
  * kernel: eeprom: (CVE-2024-35848)
  * kernel: ice: (CVE-2024-35911)
  * kernel: platform/x86: (CVE-2023-52864)
  * kernel: i40e: (CVE-2024-36020)
  * kernel: rtnetlink: (CVE-2024-36017)
  * kernel: net: multiple flaws (CVE-2024-36929, CVE-2024-36971, CVE-2021-47606, CVE-2024-38558, CVE-2024-40928, CVE-2024-40954)
  * kernel: ipvlan: (CVE-2024-33621)
  * kernel: tcp: (CVE-2024-37356)
  * kernel: virtio: (CVE-2024-37353)
  * kernel: tls: (CVE-2024-36489)
  * kernel: cxl/region: (CVE-2024-38391)
  * kernel: bonding: (CVE-2024-39487)
  * kernel: netns: (CVE-2024-40958)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, an…&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.  
Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: phy: (CVE-2024-26600)
  * kernel: netfilter: multiple flaws (CVE-2024-26808, CVE-2024-27065, CVE-2024-35899, CVE-2024-36005)
  * kernel: cifs: (CVE-2024-26828)
  * kernel: wifi: multiple flaws (CVE-2024-26897, CVE-2024-27052, CVE-2024-27049, CVE-2023-52651, CVE-2024-35789, CVE-2024-27434, CVE-2024-35845, CVE-2024-35937, CVE-2024-36941, CVE-2024-36922, CVE-2024-36921, CVE-2024-38575)
  * kernel: nfs: (CVE-2024-26868)
  * kernel: igc: (CVE-2024-26853)
  * kernel: dmaengine/idxd: (CVE-2024-21823)
  * kernel: ipv6: multiple flaws (CVE-2024-27417, CVE-2024-35969, CVE-2024-36903, CVE-2024-40961)
  * kernel: vt: (CVE-2024-35823)
  * kernel: efi: (CVE-2024-35800)
  * kernel: mlxsw: (CVE-2024-35852)
  * kernel: eeprom: (CVE-2024-35848)
  * kernel: ice: (CVE-2024-35911)
  * kernel: platform/x86: (CVE-2023-52864)
  * kernel: i40e: (CVE-2024-36020)
  * kernel: rtnetlink: (CVE-2024-36017)
  * kernel: net: multiple flaws (CVE-2024-36929, CVE-2024-36971, CVE-2021-47606, CVE-2024-38558, CVE-2024-40928, CVE-2024-40954)
  * kernel: ipvlan: (CVE-2024-33621)
  * kernel: tcp: (CVE-2024-37356)
  * kernel: virtio: (CVE-2024-37353)
  * kernel: tls: (CVE-2024-36489)
  * kernel: cxl/region: (CVE-2024-38391)
  * kernel: bonding: (CVE-2024-39487)
  * kernel: netns: (CVE-2024-40958)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, an…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2024:5363</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-40958</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-40958</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-40958</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0613 — 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-0613</link>
      <description>certfr-2024-avi-0613</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0613</guid>
    </item>
    <item>
      <title>OESA-2024-2292 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-2292</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: 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;
octeontx2-af: Use separate handlers for interrupts&#13;
&#13;
For PF to AF interrupt vector and VF to AF vector same
interrupt handler is registered which is causing race condition.
When two interrupts are raised to two CPUs at same time
then two cores serve same event corrupting the data.(CVE-2024-27030)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
media: go7007: fix a memleak in go7007_load_encoder&#13;
&#13;
In go7007_load_encoder, bounce(i.e. go-&amp;amp;gt;boot_fw), is allocated without
a deallocation thereafter. After the following call chain:&#13;
&#13;
saa7134_go7007_init
  |-&amp;amp;gt; go7007_boot_encoder
        |-&amp;amp;gt; go7007_load_encoder
  |-&amp;amp;gt; kfree(go)&#13;
&#13;
go is freed and thus bounce is leaked.(CVE-2024-27074)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
netfilter: nf_tables: use timestamp to check for set element timeout&#13;
&#13;
Add a timestamp field at the beginning of the transaction, store it
in the nftables per-netns area.&#13;
&#13;
Update set backend .insert, .deactivate and sync gc path to use the
timestamp, this avoids that an element expires while control plane
transaction is still unfinished.&#13;
&#13;
.lookup and .update, which are used from packet path, still use the
current time to check if the element has expired. And .get path and dump
also since this runs lockless under rcu read size lock. Then, ther…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: 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;
octeontx2-af: Use separate handlers for interrupts&#13;
&#13;
For PF to AF interrupt vector and VF to AF vector same
interrupt handler is registered which is causing race condition.
When two interrupts are raised to two CPUs at same time
then two cores serve same event corrupting the data.(CVE-2024-27030)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
media: go7007: fix a memleak in go7007_load_encoder&#13;
&#13;
In go7007_load_encoder, bounce(i.e. go-&amp;amp;gt;boot_fw), is allocated without
a deallocation thereafter. After the following call chain:&#13;
&#13;
saa7134_go7007_init
  |-&amp;amp;gt; go7007_boot_encoder
        |-&amp;amp;gt; go7007_load_encoder
  |-&amp;amp;gt; kfree(go)&#13;
&#13;
go is freed and thus bounce is leaked.(CVE-2024-27074)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
netfilter: nf_tables: use timestamp to check for set element timeout&#13;
&#13;
Add a timestamp field at the beginning of the transaction, store it
in the nftables per-netns area.&#13;
&#13;
Update set backend .insert, .deactivate and sync gc path to use the
timestamp, this avoids that an element expires while control plane
transaction is still unfinished.&#13;
&#13;
.lookup and .update, which are used from packet path, still use the
current time to check if the element has expired. And .get path and dump
also since this runs lockless under rcu read size lock. Then, ther…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-2292</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-40958</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-40958</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 157 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netns: Make get_net_ns() handle zero refcount net Syzkaller hit a warning: refcount_t: addition on 0; use-after-free. WARNING: CPU: 3 PID: 7890 at lib/refcount.c:25 refcount_warn_saturate+0xdf/0x1d0 Modules linked in: CPU: 3 PID: 7890 Comm: tun Not tainted 6.10.0-rc3-00100-gcaa4f9578aba-dirty #310 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 RIP: 0010:refcount_warn_saturate+0xdf/0x1d0 Code: 41 49 04 31 ff 89 de e8 9f 1e cd fe 84 db 75 9c e8 76 26 cd fe c6 05 b6 41 49 04 01 90 48 c7 c7 b8 8e 25 86 e8 d2 05 b5 fe 90 &amp;lt;0f&amp;gt; 0b 90 90 e9 79 ff ff ff e8 53 26 cd fe 0f b6 1 RSP: 0018:ffff8881067b7da0 EFLAGS: 00010286 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff811c72ac RDX: ffff8881026a2140 RSI: ffffffff811c72b5 RDI: 0000000000000001 RBP: ffff8881067b7db0 R08: 0000000000000000 R09: 205b5d3730353139 R10: 0000000000000000 R11: 205d303938375420 R12: ffff8881086500c4 R13: ffff8881086500c4 R14: ffff8881086500b0 R15: ffff888108650040 FS:  00007f5b2961a4c0(0000) GS:ffff88823bd00000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000055d7ed36fd18 CR3: 00000001482f6000 CR4: 00000000000006f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  &amp;lt;TASK&amp;gt;  ? show_regs+0xa3/0xc0  ? __warn+0xa5/0x1c0  ? refcount_warn_saturate+0xdf/0x1d0  ? report_bug+0x1fc/0x2d…&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 157 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netns: Make get_net_ns() handle zero refcount net Syzkaller hit a warning: refcount_t: addition on 0; use-after-free. WARNING: CPU: 3 PID: 7890 at lib/refcount.c:25 refcount_warn_saturate+0xdf/0x1d0 Modules linked in: CPU: 3 PID: 7890 Comm: tun Not tainted 6.10.0-rc3-00100-gcaa4f9578aba-dirty #310 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 RIP: 0010:refcount_warn_saturate+0xdf/0x1d0 Code: 41 49 04 31 ff 89 de e8 9f 1e cd fe 84 db 75 9c e8 76 26 cd fe c6 05 b6 41 49 04 01 90 48 c7 c7 b8 8e 25 86 e8 d2 05 b5 fe 90 &amp;lt;0f&amp;gt; 0b 90 90 e9 79 ff ff ff e8 53 26 cd fe 0f b6 1 RSP: 0018:ffff8881067b7da0 EFLAGS: 00010286 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff811c72ac RDX: ffff8881026a2140 RSI: ffffffff811c72b5 RDI: 0000000000000001 RBP: ffff8881067b7db0 R08: 0000000000000000 R09: 205b5d3730353139 R10: 0000000000000000 R11: 205d303938375420 R12: ffff8881086500c4 R13: ffff8881086500c4 R14: ffff8881086500b0 R15: ffff888108650040 FS:  00007f5b2961a4c0(0000) GS:ffff88823bd00000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000055d7ed36fd18 CR3: 00000001482f6000 CR4: 00000000000006f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  &amp;lt;TASK&amp;gt;  ? show_regs+0xa3/0xc0  ? __warn+0xa5/0x1c0  ? refcount_warn_saturate+0xdf/0x1d0  ? report_bug+0x1fc/0x2d…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-40958</guid>
    </item>
  </channel>
</rss>
