<?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://vulnerability.circl.lu</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>Sun, 04 Oct 2026 14:30:36 +0000</lastBuildDate>
    <item>
      <title>CERTFR-2025-AVI-0529 — 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://vulnerability.circl.lu/vuln/CERTFR-2025-AVI-0529</link>
      <description>CERTFR-2025-AVI-0529</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/CERTFR-2025-AVI-0529</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-53121</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2023-53121</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2023-53121</guid>
    </item>
    <item>
      <title>fkie_cve-2023-53121</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2023-53121</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tcp: tcp_make_synack() can be called from process context&lt;/p&gt;
&lt;p&gt;tcp_rtx_synack() now could be called in process context as explained in
0a375c822497 (&amp;#34;tcp: tcp_rtx_synack() can be called from process
context&amp;#34;).&lt;/p&gt;
&lt;p&gt;tcp_rtx_synack() might call tcp_make_synack(), which will touch per-CPU
variables with preemption enabled. This causes the following BUG:&lt;/p&gt;
&lt;p&gt;BUG: using __this_cpu_add() in preemptible [00000000] code: ThriftIO1/5464
    caller is tcp_make_synack+0x841/0xac0
    Call Trace:
     &amp;lt;TASK&amp;gt;
     dump_stack_lvl+0x10d/0x1a0
     check_preemption_disabled+0x104/0x110
     tcp_make_synack+0x841/0xac0
     tcp_v6_send_synack+0x5c/0x450
     tcp_rtx_synack+0xeb/0x1f0
     inet_rtx_syn_ack+0x34/0x60
     tcp_check_req+0x3af/0x9e0
     tcp_rcv_state_process+0x59b/0x2030
     tcp_v6_do_rcv+0x5f5/0x700
     release_sock+0x3a/0xf0
     tcp_sendmsg+0x33/0x40
     ____sys_sendmsg+0x2f2/0x490
     __sys_sendmsg+0x184/0x230
     do_syscall_64+0x3d/0x90&lt;/p&gt;
&lt;p&gt;Avoid calling __TCP_INC_STATS() with will touch per-cpu variables. Use
TCP_INC_STATS() which is safe to be called from context switch.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tcp: tcp_make_synack() can be called from process context&lt;/p&gt;
&lt;p&gt;tcp_rtx_synack() now could be called in process context as explained in
0a375c822497 (&amp;#34;tcp: tcp_rtx_synack() can be called from process
context&amp;#34;).&lt;/p&gt;
&lt;p&gt;tcp_rtx_synack() might call tcp_make_synack(), which will touch per-CPU
variables with preemption enabled. This causes the following BUG:&lt;/p&gt;
&lt;p&gt;BUG: using __this_cpu_add() in preemptible [00000000] code: ThriftIO1/5464
    caller is tcp_make_synack+0x841/0xac0
    Call Trace:
     &amp;lt;TASK&amp;gt;
     dump_stack_lvl+0x10d/0x1a0
     check_preemption_disabled+0x104/0x110
     tcp_make_synack+0x841/0xac0
     tcp_v6_send_synack+0x5c/0x450
     tcp_rtx_synack+0xeb/0x1f0
     inet_rtx_syn_ack+0x34/0x60
     tcp_check_req+0x3af/0x9e0
     tcp_rcv_state_process+0x59b/0x2030
     tcp_v6_do_rcv+0x5f5/0x700
     release_sock+0x3a/0xf0
     tcp_sendmsg+0x33/0x40
     ____sys_sendmsg+0x2f2/0x490
     __sys_sendmsg+0x184/0x230
     do_syscall_64+0x3d/0x90&lt;/p&gt;
&lt;p&gt;Avoid calling __TCP_INC_STATS() with will touch per-cpu variables. Use
TCP_INC_STATS() which is safe to be called from context switch.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2023-53121</guid>
    </item>
    <item>
      <title>GHSA-cwj5-qqpc-pw3v</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-cwj5-qqpc-pw3v</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tcp: tcp_make_synack() can be called from process context&lt;/p&gt;
&lt;p&gt;tcp_rtx_synack() now could be called in process context as explained in
0a375c822497 (&amp;#34;tcp: tcp_rtx_synack() can be called from process
context&amp;#34;).&lt;/p&gt;
&lt;p&gt;tcp_rtx_synack() might call tcp_make_synack(), which will touch per-CPU
variables with preemption enabled. This causes the following BUG:&lt;/p&gt;
&lt;p&gt;BUG: using __this_cpu_add() in preemptible [00000000] code: ThriftIO1/5464
    caller is tcp_make_synack+0x841/0xac0
    Call Trace:
     &amp;lt;TASK&amp;gt;
     dump_stack_lvl+0x10d/0x1a0
     check_preemption_disabled+0x104/0x110
     tcp_make_synack+0x841/0xac0
     tcp_v6_send_synack+0x5c/0x450
     tcp_rtx_synack+0xeb/0x1f0
     inet_rtx_syn_ack+0x34/0x60
     tcp_check_req+0x3af/0x9e0
     tcp_rcv_state_process+0x59b/0x2030
     tcp_v6_do_rcv+0x5f5/0x700
     release_sock+0x3a/0xf0
     tcp_sendmsg+0x33/0x40
     ____sys_sendmsg+0x2f2/0x490
     __sys_sendmsg+0x184/0x230
     do_syscall_64+0x3d/0x90&lt;/p&gt;
&lt;p&gt;Avoid calling __TCP_INC_STATS() with will touch per-cpu variables. Use
TCP_INC_STATS() which is safe to be called from context switch.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tcp: tcp_make_synack() can be called from process context&lt;/p&gt;
&lt;p&gt;tcp_rtx_synack() now could be called in process context as explained in
0a375c822497 (&amp;#34;tcp: tcp_rtx_synack() can be called from process
context&amp;#34;).&lt;/p&gt;
&lt;p&gt;tcp_rtx_synack() might call tcp_make_synack(), which will touch per-CPU
variables with preemption enabled. This causes the following BUG:&lt;/p&gt;
&lt;p&gt;BUG: using __this_cpu_add() in preemptible [00000000] code: ThriftIO1/5464
    caller is tcp_make_synack+0x841/0xac0
    Call Trace:
     &amp;lt;TASK&amp;gt;
     dump_stack_lvl+0x10d/0x1a0
     check_preemption_disabled+0x104/0x110
     tcp_make_synack+0x841/0xac0
     tcp_v6_send_synack+0x5c/0x450
     tcp_rtx_synack+0xeb/0x1f0
     inet_rtx_syn_ack+0x34/0x60
     tcp_check_req+0x3af/0x9e0
     tcp_rcv_state_process+0x59b/0x2030
     tcp_v6_do_rcv+0x5f5/0x700
     release_sock+0x3a/0xf0
     tcp_sendmsg+0x33/0x40
     ____sys_sendmsg+0x2f2/0x490
     __sys_sendmsg+0x184/0x230
     do_syscall_64+0x3d/0x90&lt;/p&gt;
&lt;p&gt;Avoid calling __TCP_INC_STATS() with will touch per-cpu variables. Use
TCP_INC_STATS() which is safe to be called from context switch.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-cwj5-qqpc-pw3v</guid>
    </item>
    <item>
      <title>RHSA-2023:6583 — security update for kernel</title>
      <link>https://vulnerability.circl.lu/vuln/rhsa-2023:6583</link>
      <description>&lt;p&gt;security update for kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;security update for kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/rhsa-2023:6583</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01983-1 — Security update for the Linux Kernel</title>
      <link>https://vulnerability.circl.lu/vuln/suse-su-2025:01983-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/suse-su-2025:01983-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-53121</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2023-53121</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 153 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tcp: tcp_make_synack() can be called from process context tcp_rtx_synack() now could be called in process context as explained in 0a375c822497 (&amp;#34;tcp: tcp_rtx_synack() can be called from process context&amp;#34;). tcp_rtx_synack() might call tcp_make_synack(), which will touch per-CPU variables with preemption enabled. This causes the following BUG:     BUG: using __this_cpu_add() in preemptible [00000000] code: ThriftIO1/5464     caller is tcp_make_synack+0x841/0xac0     Call Trace:      &amp;lt;TASK&amp;gt;      dump_stack_lvl+0x10d/0x1a0      check_preemption_disabled+0x104/0x110      tcp_make_synack+0x841/0xac0      tcp_v6_send_synack+0x5c/0x450      tcp_rtx_synack+0xeb/0x1f0      inet_rtx_syn_ack+0x34/0x60      tcp_check_req+0x3af/0x9e0      tcp_rcv_state_process+0x59b/0x2030      tcp_v6_do_rcv+0x5f5/0x700      release_sock+0x3a/0xf0      tcp_sendmsg+0x33/0x40      ____sys_sendmsg+0x2f2/0x490      __sys_sendmsg+0x184/0x230      do_syscall_64+0x3d/0x90 Avoid calling __TCP_INC_STATS() with will touch per-cpu variables. Use TCP_INC_STATS() which is safe to be called from context switch.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 153 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tcp: tcp_make_synack() can be called from process context tcp_rtx_synack() now could be called in process context as explained in 0a375c822497 (&amp;#34;tcp: tcp_rtx_synack() can be called from process context&amp;#34;). tcp_rtx_synack() might call tcp_make_synack(), which will touch per-CPU variables with preemption enabled. This causes the following BUG:     BUG: using __this_cpu_add() in preemptible [00000000] code: ThriftIO1/5464     caller is tcp_make_synack+0x841/0xac0     Call Trace:      &amp;lt;TASK&amp;gt;      dump_stack_lvl+0x10d/0x1a0      check_preemption_disabled+0x104/0x110      tcp_make_synack+0x841/0xac0      tcp_v6_send_synack+0x5c/0x450      tcp_rtx_synack+0xeb/0x1f0      inet_rtx_syn_ack+0x34/0x60      tcp_check_req+0x3af/0x9e0      tcp_rcv_state_process+0x59b/0x2030      tcp_v6_do_rcv+0x5f5/0x700      release_sock+0x3a/0xf0      tcp_sendmsg+0x33/0x40      ____sys_sendmsg+0x2f2/0x490      __sys_sendmsg+0x184/0x230      do_syscall_64+0x3d/0x90 Avoid calling __TCP_INC_STATS() with will touch per-cpu variables. Use TCP_INC_STATS() which is safe to be called from context switch.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2023-53121</guid>
    </item>
  </channel>
</rss>
