<?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 14:39:02 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-36938</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-36938</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-36938</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0496 — 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-0496</link>
      <description>certfr-2024-avi-0496</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0496</guid>
    </item>
    <item>
      <title>OESA-2024-2029 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-2029</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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;
mlxsw: spectrum_acl_tcam: Fix stack corruption&#13;
&#13;
When tc filters are first added to a net device, the corresponding local
port gets bound to an ACL group in the device. The group contains a list
of ACLs. In turn, each ACL points to a different TCAM region where the
filters are stored. During forwarding, the ACLs are sequentially
evaluated until a match is found.&#13;
&#13;
One reason to place filters in different regions is when they are added
with decreasing priorities and in an alternating order so that two
consecutive filters can never fit in the same region because of their
key usage.&#13;
&#13;
In Spectrum-2 and newer ASICs the firmware started to report that the
maximum number of ACLs in a group is more than 16, but the layout of the
register that configures ACL groups (PAGT) was not updated to account
for that. It is therefore possible to hit stack corruption [1] in the
rare case where more than 16 ACLs in a group are required.&#13;
&#13;
Fix by limiting the maximum ACL group size to the minimum between what
the firmware reports and the maximum ACLs that fit in the PAGT register.&#13;
&#13;
Add a test case to make sure the machine does not crash when this
condition is hit.&#13;
&#13;
[1]
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: mlxsw_sp_acl_tcam_group_update+0x116/0x120
[...]
 dump_stack_lvl+0x36/0x50
 panic+0x305/0x330
 __stack…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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;
mlxsw: spectrum_acl_tcam: Fix stack corruption&#13;
&#13;
When tc filters are first added to a net device, the corresponding local
port gets bound to an ACL group in the device. The group contains a list
of ACLs. In turn, each ACL points to a different TCAM region where the
filters are stored. During forwarding, the ACLs are sequentially
evaluated until a match is found.&#13;
&#13;
One reason to place filters in different regions is when they are added
with decreasing priorities and in an alternating order so that two
consecutive filters can never fit in the same region because of their
key usage.&#13;
&#13;
In Spectrum-2 and newer ASICs the firmware started to report that the
maximum number of ACLs in a group is more than 16, but the layout of the
register that configures ACL groups (PAGT) was not updated to account
for that. It is therefore possible to hit stack corruption [1] in the
rare case where more than 16 ACLs in a group are required.&#13;
&#13;
Fix by limiting the maximum ACL group size to the minimum between what
the firmware reports and the maximum ACLs that fit in the PAGT register.&#13;
&#13;
Add a test case to make sure the machine does not crash when this
condition is hit.&#13;
&#13;
[1]
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: mlxsw_sp_acl_tcam_group_update+0x116/0x120
[...]
 dump_stack_lvl+0x36/0x50
 panic+0x305/0x330
 __stack…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-2029</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-36938</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-36938</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: bpf, skmsg: Fix NULL pointer dereference in sk_psock_skb_ingress_enqueue Fix NULL pointer data-races in sk_psock_skb_ingress_enqueue() which syzbot reported [1]. [1] BUG: KCSAN: data-race in sk_psock_drop / sk_psock_skb_ingress_enqueue write to 0xffff88814b3278b8 of 8 bytes by task 10724 on cpu 1:  sk_psock_stop_verdict net/core/skmsg.c:1257 [inline]  sk_psock_drop+0x13e/0x1f0 net/core/skmsg.c:843  sk_psock_put include/linux/skmsg.h:459 [inline]  sock_map_close+0x1a7/0x260 net/core/sock_map.c:1648  unix_release+0x4b/0x80 net/unix/af_unix.c:1048  __sock_release net/socket.c:659 [inline]  sock_close+0x68/0x150 net/socket.c:1421  __fput+0x2c1/0x660 fs/file_table.c:422  __fput_sync+0x44/0x60 fs/file_table.c:507  __do_sys_close fs/open.c:1556 [inline]  __se_sys_close+0x101/0x1b0 fs/open.c:1541  __x64_sys_close+0x1f/0x30 fs/open.c:1541  do_syscall_64+0xd3/0x1d0  entry_SYSCALL_64_after_hwframe+0x6d/0x75 read to 0xffff88814b3278b8 of 8 bytes by task 10713 on cpu 0:  sk_psock_data_ready include/linux/skmsg.h:464 [inline]  sk_psock_skb_ingress_enqueue+0x32d/0x390 net/core/skmsg.c:555  sk_psock_skb_ingress_self+0x185/0x1e0 net/core/skmsg.c:606  sk_psock_verdict_apply net/core/skmsg.c:1008 [inline]  sk_psock_verdict_recv+0x3e4/0x4a0 net/core/skmsg.c:1202  unix_read_skb net/unix/af_unix.c:2546 [inline]  unix_stream_read_skb+0x9e/0xf0 net/unix/af_unix.c:2682  sk_psock_verdict_data_ready+0x77/0x220 net/core/skmsg.c:1223  u…&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: bpf, skmsg: Fix NULL pointer dereference in sk_psock_skb_ingress_enqueue Fix NULL pointer data-races in sk_psock_skb_ingress_enqueue() which syzbot reported [1]. [1] BUG: KCSAN: data-race in sk_psock_drop / sk_psock_skb_ingress_enqueue write to 0xffff88814b3278b8 of 8 bytes by task 10724 on cpu 1:  sk_psock_stop_verdict net/core/skmsg.c:1257 [inline]  sk_psock_drop+0x13e/0x1f0 net/core/skmsg.c:843  sk_psock_put include/linux/skmsg.h:459 [inline]  sock_map_close+0x1a7/0x260 net/core/sock_map.c:1648  unix_release+0x4b/0x80 net/unix/af_unix.c:1048  __sock_release net/socket.c:659 [inline]  sock_close+0x68/0x150 net/socket.c:1421  __fput+0x2c1/0x660 fs/file_table.c:422  __fput_sync+0x44/0x60 fs/file_table.c:507  __do_sys_close fs/open.c:1556 [inline]  __se_sys_close+0x101/0x1b0 fs/open.c:1541  __x64_sys_close+0x1f/0x30 fs/open.c:1541  do_syscall_64+0xd3/0x1d0  entry_SYSCALL_64_after_hwframe+0x6d/0x75 read to 0xffff88814b3278b8 of 8 bytes by task 10713 on cpu 0:  sk_psock_data_ready include/linux/skmsg.h:464 [inline]  sk_psock_skb_ingress_enqueue+0x32d/0x390 net/core/skmsg.c:555  sk_psock_skb_ingress_self+0x185/0x1e0 net/core/skmsg.c:606  sk_psock_verdict_apply net/core/skmsg.c:1008 [inline]  sk_psock_verdict_recv+0x3e4/0x4a0 net/core/skmsg.c:1202  unix_read_skb net/unix/af_unix.c:2546 [inline]  unix_stream_read_skb+0x9e/0xf0 net/unix/af_unix.c:2682  sk_psock_verdict_data_ready+0x77/0x220 net/core/skmsg.c:1223  u…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-36938</guid>
    </item>
  </channel>
</rss>
