<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-01T14:47:05.320336+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/CERTFR-2025-AVI-1047</id>
    <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>
    <updated>2026-10-01T14:47:05.796325+00:00</updated>
    <content>CERTFR-2025-AVI-1047</content>
    <link href="https://vulnerability.circl.lu/vuln/CERTFR-2025-AVI-1047"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/bdu:2026-08795</id>
    <title>bdu:2026-08795</title>
    <updated>2026-10-01T14:47:05.796420+00:00</updated>
    <content>bdu:2026-08795</content>
    <link href="https://vulnerability.circl.lu/vuln/bdu:2026-08795"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/bell-cve-2023-53635</id>
    <title>BELL-CVE-2023-53635</title>
    <updated>2026-10-01T14:47:05.796448+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/bell-cve-2023-53635"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2023-53635</id>
    <title>fkie_cve-2023-53635</title>
    <updated>2026-10-01T14:47:05.796498+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>netfilter: conntrack: fix wrong ct-&gt;timeout value</p>
<p>(struct nf_conn)-&gt;timeout is an interval before the conntrack
confirmed.  After confirmed, it becomes a timestamp.</p>
<p>It is observed that timeout of an unconfirmed conntrack:
- Set by calling ctnetlink_change_timeout(). As a result,
  `nfct_time_stamp` was wrongly added to `ct-&gt;timeout` twice.
- Get by calling ctnetlink_dump_timeout(). As a result,
  `nfct_time_stamp` was wrongly subtracted.</p>
<p>Call Trace:
 &lt;TASK&gt;
 dump_stack_lvl
 ctnetlink_dump_timeout
 __ctnetlink_glue_build
 ctnetlink_glue_build
 __nfqnl_enqueue_packet
 nf_queue
 nf_hook_slow
 ip_mc_output
 ? __pfx_ip_finish_output
 ip_send_skb
 ? __pfx_dst_output
 udp_send_skb
 udp_sendmsg
 ? __pfx_ip_generic_getfrag
 sock_sendmsg</p>
<p>Separate the 2 cases in:
- Setting `ct-&gt;timeout` in __nf_ct_set_timeout().
- Getting `ct-&gt;timeout` in ctnetlink_dump_timeout().</p>
<p>Pablo appends:</p>
<p>Update ctnetlink to set up the timeout _after_ the IPS_CONFIRMED flag is
set on, otherwise conntrack creation via ctnetlink breaks.</p>
<p>Note that the problem described in this patch occurs since the
introduction of the nfnetlink_queue conntrack support, select a
sufficiently old Fixes: tag for -stable kernel to pick up this fix.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2023-53635"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-v8v9-wq25-mffx</id>
    <title>GHSA-v8v9-wq25-mffx</title>
    <updated>2026-10-01T14:47:05.796592+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>netfilter: conntrack: fix wrong ct-&gt;timeout value</p>
<p>(struct nf_conn)-&gt;timeout is an interval before the conntrack
confirmed.  After confirmed, it becomes a timestamp.</p>
<p>It is observed that timeout of an unconfirmed conntrack:
- Set by calling ctnetlink_change_timeout(). As a result,
  `nfct_time_stamp` was wrongly added to `ct-&gt;timeout` twice.
- Get by calling ctnetlink_dump_timeout(). As a result,
  `nfct_time_stamp` was wrongly subtracted.</p>
<p>Call Trace:
 &lt;TASK&gt;
 dump_stack_lvl
 ctnetlink_dump_timeout
 __ctnetlink_glue_build
 ctnetlink_glue_build
 __nfqnl_enqueue_packet
 nf_queue
 nf_hook_slow
 ip_mc_output
 ? __pfx_ip_finish_output
 ip_send_skb
 ? __pfx_dst_output
 udp_send_skb
 udp_sendmsg
 ? __pfx_ip_generic_getfrag
 sock_sendmsg</p>
<p>Separate the 2 cases in:
- Setting `ct-&gt;timeout` in __nf_ct_set_timeout().
- Getting `ct-&gt;timeout` in ctnetlink_dump_timeout().</p>
<p>Pablo appends:</p>
<p>Update ctnetlink to set up the timeout _after_ the IPS_CONFIRMED flag is
set on, otherwise conntrack creation via ctnetlink breaks.</p>
<p>Note that the problem described in this patch occurs since the
introduction of the nfnetlink_queue conntrack support, select a
sufficiently old Fixes: tag for -stable kernel to pick up this fix.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-v8v9-wq25-mffx"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/rhsa-2023:6583</id>
    <title>RHSA-2023:6583 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
    <updated>2026-10-01T14:47:05.796650+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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'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…</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/rhsa-2023:6583"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/suse-su-2025:4189-1</id>
    <title>SUSE-SU-2025:4189-1 — Security update for the Linux Kernel</title>
    <updated>2026-10-01T14:47:05.798987+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for the Linux Kernel</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/suse-su-2025:4189-1"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ubuntu-cve-2023-53635</id>
    <title>UBUNTU-CVE-2023-53635</title>
    <updated>2026-10-01T14:47:05.799220+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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, Ubuntu:16.04:LTS: linux-hwe-edge and 169 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: netfilter: conntrack: fix wrong ct-&gt;timeout value (struct nf_conn)-&gt;timeout is an interval before the conntrack confirmed.  After confirmed, it becomes a timestamp. It is observed that timeout of an unconfirmed conntrack: - Set by calling ctnetlink_change_timeout(). As a result,   `nfct_time_stamp` was wrongly added to `ct-&gt;timeout` twice. - Get by calling ctnetlink_dump_timeout(). As a result,   `nfct_time_stamp` was wrongly subtracted. Call Trace:  &lt;TASK&gt;  dump_stack_lvl  ctnetlink_dump_timeout  __ctnetlink_glue_build  ctnetlink_glue_build  __nfqnl_enqueue_packet  nf_queue  nf_hook_slow  ip_mc_output  ? __pfx_ip_finish_output  ip_send_skb  ? __pfx_dst_output  udp_send_skb  udp_sendmsg  ? __pfx_ip_generic_getfrag  sock_sendmsg Separate the 2 cases in: - Setting `ct-&gt;timeout` in __nf_ct_set_timeout(). - Getting `ct-&gt;timeout` in ctnetlink_dump_timeout(). Pablo appends: Update ctnetlink to set up the timeout _after_ the IPS_CONFIRMED flag is set on, otherwise conntrack creation via ctnetlink breaks. Note that the problem described in this patch occurs since the introduction of the nfnetlink_queue conntrack support, select a sufficiently old Fixes: tag for -stable kernel to pick up this fix.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ubuntu-cve-2023-53635"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2229</id>
    <title>WID-SEC-W-2025-2229 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-10-01T14:47:05.799803+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2229"/>
  </entry>
</feed>
