<?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:26:36 +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-40961</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-40961</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-40961</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-1961 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-1961</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;
NFSD: Fix the behavior of READ near OFFSET_MAX&#13;
&#13;
Dan Aloni reports:
&amp;amp;gt; Due to commit 8cfb9015280d (&amp;amp;quot;NFS: Always provide aligned buffers to
&amp;amp;gt; the RPC read layers&amp;amp;quot;) on the client, a read of 0xfff is aligned up
&amp;amp;gt; to server rsize of 0x1000.
&amp;amp;gt;
&amp;amp;gt; As a result, in a test where the server has a file of size
&amp;amp;gt; 0x7fffffffffffffff, and the client tries to read from the offset
&amp;amp;gt; 0x7ffffffffffff000, the read causes loff_t overflow in the server
&amp;amp;gt; and it returns an NFS code of EINVAL to the client. The client as
&amp;amp;gt; a result indefinitely retries the request.&#13;
&#13;
The Linux NFS client does not handle NFS?ERR_INVAL, even though all
NFS specifications permit servers to return that status code for a
READ.&#13;
&#13;
Instead of NFS?ERR_INVAL, have out-of-range READ requests succeed
and return a short result. Set the EOF flag in the result to prevent
the client from retrying the READ request. This behavior appears to
be consistent with Solaris NFS servers.&#13;
&#13;
Note that NFSv3 and NFSv4 use u64 offset values on the wire. These
must be converted to loff_t internally before use -- an implicit
type cast is not adequate for this purpose. Otherwise VFS checks
against sb-&amp;amp;gt;s_maxbytes do not work properly.(CVE-2022-48827)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
net: can: j1939: enhanced error handlin…&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;
NFSD: Fix the behavior of READ near OFFSET_MAX&#13;
&#13;
Dan Aloni reports:
&amp;amp;gt; Due to commit 8cfb9015280d (&amp;amp;quot;NFS: Always provide aligned buffers to
&amp;amp;gt; the RPC read layers&amp;amp;quot;) on the client, a read of 0xfff is aligned up
&amp;amp;gt; to server rsize of 0x1000.
&amp;amp;gt;
&amp;amp;gt; As a result, in a test where the server has a file of size
&amp;amp;gt; 0x7fffffffffffffff, and the client tries to read from the offset
&amp;amp;gt; 0x7ffffffffffff000, the read causes loff_t overflow in the server
&amp;amp;gt; and it returns an NFS code of EINVAL to the client. The client as
&amp;amp;gt; a result indefinitely retries the request.&#13;
&#13;
The Linux NFS client does not handle NFS?ERR_INVAL, even though all
NFS specifications permit servers to return that status code for a
READ.&#13;
&#13;
Instead of NFS?ERR_INVAL, have out-of-range READ requests succeed
and return a short result. Set the EOF flag in the result to prevent
the client from retrying the READ request. This behavior appears to
be consistent with Solaris NFS servers.&#13;
&#13;
Note that NFSv3 and NFSv4 use u64 offset values on the wire. These
must be converted to loff_t internally before use -- an implicit
type cast is not adequate for this purpose. Otherwise VFS checks
against sb-&amp;amp;gt;s_maxbytes do not work properly.(CVE-2022-48827)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
net: can: j1939: enhanced error handlin…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-1961</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-40961</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-40961</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: ipv6: prevent possible NULL deref in fib6_nh_init() syzbot reminds us that in6_dev_get() can return NULL. fib6_nh_init()     ip6_validate_gw(  &amp;amp;idev  )         ip6_route_check_nh(  idev  )             *idev = in6_dev_get(dev); // can be NULL Oops: general protection fault, probably for non-canonical address 0xdffffc00000000bc: 0000 [#1] PREEMPT SMP KASAN PTI KASAN: null-ptr-deref in range [0x00000000000005e0-0x00000000000005e7] CPU: 0 PID: 11237 Comm: syz-executor.3 Not tainted 6.10.0-rc2-syzkaller-00249-gbe27b8965297 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024  RIP: 0010:fib6_nh_init+0x640/0x2160 net/ipv6/route.c:3606 Code: 00 00 fc ff df 4c 8b 64 24 58 48 8b 44 24 28 4c 8b 74 24 30 48 89 c1 48 89 44 24 28 48 8d 98 e0 05 00 00 48 89 d8 48 c1 e8 03 &amp;lt;42&amp;gt; 0f b6 04 38 84 c0 0f 85 b3 17 00 00 8b 1b 31 ff 89 de e8 b8 8b RSP: 0018:ffffc900032775a0 EFLAGS: 00010202 RAX: 00000000000000bc RBX: 00000000000005e0 RCX: 0000000000000000 RDX: 0000000000000010 RSI: ffffc90003277a54 RDI: ffff88802b3a08d8 RBP: ffffc900032778b0 R08: 00000000000002fc R09: 0000000000000000 R10: 00000000000002fc R11: 0000000000000000 R12: ffff88802b3a08b8 R13: 1ffff9200064eec8 R14: ffffc90003277a00 R15: dffffc0000000000 FS:  00007f940feb06c0(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 00000000245e8000 CR4: 00000…&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: ipv6: prevent possible NULL deref in fib6_nh_init() syzbot reminds us that in6_dev_get() can return NULL. fib6_nh_init()     ip6_validate_gw(  &amp;amp;idev  )         ip6_route_check_nh(  idev  )             *idev = in6_dev_get(dev); // can be NULL Oops: general protection fault, probably for non-canonical address 0xdffffc00000000bc: 0000 [#1] PREEMPT SMP KASAN PTI KASAN: null-ptr-deref in range [0x00000000000005e0-0x00000000000005e7] CPU: 0 PID: 11237 Comm: syz-executor.3 Not tainted 6.10.0-rc2-syzkaller-00249-gbe27b8965297 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024  RIP: 0010:fib6_nh_init+0x640/0x2160 net/ipv6/route.c:3606 Code: 00 00 fc ff df 4c 8b 64 24 58 48 8b 44 24 28 4c 8b 74 24 30 48 89 c1 48 89 44 24 28 48 8d 98 e0 05 00 00 48 89 d8 48 c1 e8 03 &amp;lt;42&amp;gt; 0f b6 04 38 84 c0 0f 85 b3 17 00 00 8b 1b 31 ff 89 de e8 b8 8b RSP: 0018:ffffc900032775a0 EFLAGS: 00010202 RAX: 00000000000000bc RBX: 00000000000005e0 RCX: 0000000000000000 RDX: 0000000000000010 RSI: ffffc90003277a54 RDI: ffff88802b3a08d8 RBP: ffffc900032778b0 R08: 00000000000002fc R09: 0000000000000000 R10: 00000000000002fc R11: 0000000000000000 R12: ffff88802b3a08b8 R13: 1ffff9200064eec8 R14: ffffc90003277a00 R15: dffffc0000000000 FS:  00007f940feb06c0(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 00000000245e8000 CR4: 00000…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-40961</guid>
    </item>
  </channel>
</rss>
