<?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>Fri, 02 Oct 2026 09:56:55 +0000</lastBuildDate>
    <item>
      <title>CERTFR-2025-AVI-1047 — 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-1047</link>
      <description>CERTFR-2025-AVI-1047</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/CERTFR-2025-AVI-1047</guid>
    </item>
    <item>
      <title>bdu:2026-03827</title>
      <link>https://vulnerability.circl.lu/vuln/bdu:2026-03827</link>
      <description>bdu:2026-03827</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bdu:2026-03827</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-53624</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2023-53624</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-53624</guid>
    </item>
    <item>
      <title>fkie_cve-2023-53624</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2023-53624</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/sched: sch_fq: fix integer overflow of &amp;#34;credit&amp;#34;&lt;/p&gt;
&lt;p&gt;if sch_fq is configured with &amp;#34;initial quantum&amp;#34; having values greater than
INT_MAX, the first assignment of &amp;#34;credit&amp;#34; does signed integer overflow to
a very negative value.
In this situation, the syzkaller script provided by Cristoph triggers the
CPU soft-lockup warning even with few sockets. It&amp;#39;s not an infinite loop,
but &amp;#34;credit&amp;#34; wasn&amp;#39;t probably meant to be minus 2Gb for each new flow.
Capping &amp;#34;initial quantum&amp;#34; to INT_MAX proved to fix the issue.&lt;/p&gt;
&lt;p&gt;v2: validation of &amp;#34;initial quantum&amp;#34; is done in fq_policy, instead of open
    coding in fq_change() _ suggested by Jakub Kicinski&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;net/sched: sch_fq: fix integer overflow of &amp;#34;credit&amp;#34;&lt;/p&gt;
&lt;p&gt;if sch_fq is configured with &amp;#34;initial quantum&amp;#34; having values greater than
INT_MAX, the first assignment of &amp;#34;credit&amp;#34; does signed integer overflow to
a very negative value.
In this situation, the syzkaller script provided by Cristoph triggers the
CPU soft-lockup warning even with few sockets. It&amp;#39;s not an infinite loop,
but &amp;#34;credit&amp;#34; wasn&amp;#39;t probably meant to be minus 2Gb for each new flow.
Capping &amp;#34;initial quantum&amp;#34; to INT_MAX proved to fix the issue.&lt;/p&gt;
&lt;p&gt;v2: validation of &amp;#34;initial quantum&amp;#34; is done in fq_policy, instead of open
    coding in fq_change() _ suggested by Jakub Kicinski&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2023-53624</guid>
    </item>
    <item>
      <title>GHSA-xhfr-4q2x-5mx4</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-xhfr-4q2x-5mx4</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/sched: sch_fq: fix integer overflow of &amp;#34;credit&amp;#34;&lt;/p&gt;
&lt;p&gt;if sch_fq is configured with &amp;#34;initial quantum&amp;#34; having values greater than
INT_MAX, the first assignment of &amp;#34;credit&amp;#34; does signed integer overflow to
a very negative value.
In this situation, the syzkaller script provided by Cristoph triggers the
CPU soft-lockup warning even with few sockets. It&amp;#39;s not an infinite loop,
but &amp;#34;credit&amp;#34; wasn&amp;#39;t probably meant to be minus 2Gb for each new flow.
Capping &amp;#34;initial quantum&amp;#34; to INT_MAX proved to fix the issue.&lt;/p&gt;
&lt;p&gt;v2: validation of &amp;#34;initial quantum&amp;#34; is done in fq_policy, instead of open
    coding in fq_change() _ suggested by Jakub Kicinski&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;net/sched: sch_fq: fix integer overflow of &amp;#34;credit&amp;#34;&lt;/p&gt;
&lt;p&gt;if sch_fq is configured with &amp;#34;initial quantum&amp;#34; having values greater than
INT_MAX, the first assignment of &amp;#34;credit&amp;#34; does signed integer overflow to
a very negative value.
In this situation, the syzkaller script provided by Cristoph triggers the
CPU soft-lockup warning even with few sockets. It&amp;#39;s not an infinite loop,
but &amp;#34;credit&amp;#34; wasn&amp;#39;t probably meant to be minus 2Gb for each new flow.
Capping &amp;#34;initial quantum&amp;#34; to INT_MAX proved to fix the issue.&lt;/p&gt;
&lt;p&gt;v2: validation of &amp;#34;initial quantum&amp;#34; is done in fq_policy, instead of open
    coding in fq_change() _ suggested by Jakub Kicinski&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-xhfr-4q2x-5mx4</guid>
    </item>
    <item>
      <title>RHSA-2023:6583 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://vulnerability.circl.lu/vuln/rhsa-2023:6583</link>
      <description>&lt;p&gt;kernel: seg6: fix the iif in the IPv6 socket control block Kernel: race when faulting a device private page in memory manager kernel: use-after-free in l1oip timer handlers kernel: Rate limit overflow messages in r8152 in intr_callback kernel: vmwgfx: use-after-free in vmw_cmd_res_check kernel: vmwgfx: use-after-free in vmw_execbuf_tie_context hw: Intel: Gather Data Sampling (GDS) side channel vulnerability kernel: Information leak in l2cap_parse_conf_req in net/bluetooth/l2cap_core.c kernel: perf: Fix perf_pending_task() UaF kernel: gpiolib: fix memory leak in gpiochip_setup_dev() kernel: memcg: fix possible use-after-free in memcg_write_event_control() kernel: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths kernel: char: tpm: Protect tpm_pm_suspend with locks kernel: ixgbevf: Fix resource leak in ixgbevf_init_module() kernel: dax: make sure inodes are flushed before destroy cache kernel: watch_queue: Actually free the watch kernel: watch_queue: Fix NULL dereference in error cleanup kernel: rtc: pl031: fix rtc features null pointer dereference kernel: tpm: fix reference counting for struct tpm_chip kernel: NFSv4: Don&amp;#39;t hold the layoutget locks across multiple RPC calls kernel: xprtrdma: treat all calls not a bcall when bc_serv is NULL kernel: net: ipv6: unexport __init-annotated seg6_hmac_init() kernel: af_unix: Fix a data-race in unix_dgram_peer_wake_me(). kernel: regulator: scmi: Fix refcount leak in scmi_regulator_probe kernel: mm/mempolicy: fix uninit-v…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: seg6: fix the iif in the IPv6 socket control block Kernel: race when faulting a device private page in memory manager kernel: use-after-free in l1oip timer handlers kernel: Rate limit overflow messages in r8152 in intr_callback kernel: vmwgfx: use-after-free in vmw_cmd_res_check kernel: vmwgfx: use-after-free in vmw_execbuf_tie_context hw: Intel: Gather Data Sampling (GDS) side channel vulnerability kernel: Information leak in l2cap_parse_conf_req in net/bluetooth/l2cap_core.c kernel: perf: Fix perf_pending_task() UaF kernel: gpiolib: fix memory leak in gpiochip_setup_dev() kernel: memcg: fix possible use-after-free in memcg_write_event_control() kernel: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths kernel: char: tpm: Protect tpm_pm_suspend with locks kernel: ixgbevf: Fix resource leak in ixgbevf_init_module() kernel: dax: make sure inodes are flushed before destroy cache kernel: watch_queue: Actually free the watch kernel: watch_queue: Fix NULL dereference in error cleanup kernel: rtc: pl031: fix rtc features null pointer dereference kernel: tpm: fix reference counting for struct tpm_chip kernel: NFSv4: Don&amp;#39;t hold the layoutget locks across multiple RPC calls kernel: xprtrdma: treat all calls not a bcall when bc_serv is NULL kernel: net: ipv6: unexport __init-annotated seg6_hmac_init() kernel: af_unix: Fix a data-race in unix_dgram_peer_wake_me(). kernel: regulator: scmi: Fix refcount leak in scmi_regulator_probe kernel: mm/mempolicy: fix uninit-v…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/rhsa-2023:6583</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:4189-1 — Security update for the Linux Kernel</title>
      <link>https://vulnerability.circl.lu/vuln/suse-su-2025:4189-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:4189-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-53624</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2023-53624</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 162 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_fq: fix integer overflow of &amp;#34;credit&amp;#34; if sch_fq is configured with &amp;#34;initial quantum&amp;#34; having values greater than INT_MAX, the first assignment of &amp;#34;credit&amp;#34; does signed integer overflow to a very negative value. In this situation, the syzkaller script provided by Cristoph triggers the CPU soft-lockup warning even with few sockets. It&amp;#39;s not an infinite loop, but &amp;#34;credit&amp;#34; wasn&amp;#39;t probably meant to be minus 2Gb for each new flow. Capping &amp;#34;initial quantum&amp;#34; to INT_MAX proved to fix the issue. v2: validation of &amp;#34;initial quantum&amp;#34; is done in fq_policy, instead of open     coding in fq_change() _ suggested by Jakub Kicinski&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 162 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_fq: fix integer overflow of &amp;#34;credit&amp;#34; if sch_fq is configured with &amp;#34;initial quantum&amp;#34; having values greater than INT_MAX, the first assignment of &amp;#34;credit&amp;#34; does signed integer overflow to a very negative value. In this situation, the syzkaller script provided by Cristoph triggers the CPU soft-lockup warning even with few sockets. It&amp;#39;s not an infinite loop, but &amp;#34;credit&amp;#34; wasn&amp;#39;t probably meant to be minus 2Gb for each new flow. Capping &amp;#34;initial quantum&amp;#34; to INT_MAX proved to fix the issue. v2: validation of &amp;#34;initial quantum&amp;#34; is done in fq_policy, instead of open     coding in fq_change() _ suggested by Jakub Kicinski&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2023-53624</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2229 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2229</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und andere nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und andere nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2229</guid>
    </item>
  </channel>
</rss>
