<?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-02T20:14:23.240207+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-2026-AVI-0108</id>
    <title>CERTFR-2026-AVI-0108 — 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-02T20:14:25.230022+00:00</updated>
    <content>CERTFR-2026-AVI-0108</content>
    <link href="https://vulnerability.circl.lu/vuln/CERTFR-2026-AVI-0108"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/bdu:2026-10313</id>
    <title>bdu:2026-10313</title>
    <updated>2026-10-02T20:14:25.230155+00:00</updated>
    <content>bdu:2026-10313</content>
    <link href="https://vulnerability.circl.lu/vuln/bdu:2026-10313"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/bell-cve-2023-53832</id>
    <title>BELL-CVE-2023-53832</title>
    <updated>2026-10-02T20:14:25.230195+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-53832"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2023-53832</id>
    <title>fkie_cve-2023-53832</title>
    <updated>2026-10-02T20:14:25.230292+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>md/raid10: fix null-ptr-deref in raid10_sync_request</p>
<p>init_resync() inits mempool and sets conf-&gt;have_replacemnt at the beginning
of sync, close_sync() frees the mempool when sync is completed.</p>
<p>After [1] recovery might be skipped and init_resync() is called but
close_sync() is not. null-ptr-deref occurs with r10bio-&gt;dev[i].repl_bio.</p>
<p>The following is one way to reproduce the issue.</p>
<p>1) create a array, wait for resync to complete, mddev-&gt;recovery_cp is set
     to MaxSector.
  2) recovery is woken and it is skipped. conf-&gt;have_replacement is set to
     0 in init_resync(). close_sync() not called.
  3) some io errors and rdev A is set to WantReplacement.
  4) a new device is added and set to A's replacement.
  5) recovery is woken, A have replacement, but conf-&gt;have_replacemnt is
     0. r10bio-&gt;dev[i].repl_bio will not be alloced and null-ptr-deref
     occurs.</p>
<p>Fix it by not calling init_resync() if recovery skipped.</p>
<p>[1] commit 7e83ccbecd60 ("md/raid10: Allow skipping recovery when clean arrays are assembled")</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2023-53832"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-f28c-m9h4-3wr6</id>
    <title>GHSA-f28c-m9h4-3wr6</title>
    <updated>2026-10-02T20:14:25.230394+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>md/raid10: fix null-ptr-deref in raid10_sync_request</p>
<p>init_resync() inits mempool and sets conf-&gt;have_replacemnt at the beginning
of sync, close_sync() frees the mempool when sync is completed.</p>
<p>After [1] recovery might be skipped and init_resync() is called but
close_sync() is not. null-ptr-deref occurs with r10bio-&gt;dev[i].repl_bio.</p>
<p>The following is one way to reproduce the issue.</p>
<p>1) create a array, wait for resync to complete, mddev-&gt;recovery_cp is set
     to MaxSector.
  2) recovery is woken and it is skipped. conf-&gt;have_replacement is set to
     0 in init_resync(). close_sync() not called.
  3) some io errors and rdev A is set to WantReplacement.
  4) a new device is added and set to A's replacement.
  5) recovery is woken, A have replacement, but conf-&gt;have_replacemnt is
     0. r10bio-&gt;dev[i].repl_bio will not be alloced and null-ptr-deref
     occurs.</p>
<p>Fix it by not calling init_resync() if recovery skipped.</p>
<p>[1] commit 7e83ccbecd60 ("md/raid10: Allow skipping recovery when clean arrays are assembled")</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-f28c-m9h4-3wr6"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/oesa-2026-1231</id>
    <title>OESA-2026-1231 — kernel security update</title>
    <updated>2026-10-02T20:14:25.230464+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:20.03-LTS-SP4: kernel</p>
<p>The Linux Kernel, the operating system core itself.

Security Fix(es):</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>scsi: libsas: Fix use-after-free bug in smp_execute_task_sg()</p>
<p>When executing SMP task failed, the smp_execute_task_sg() calls del_timer()
to delete &amp;quot;slow_task-&amp;gt;timer&amp;quot;. However, if the timer handler
sas_task_internal_timedout() is running, the del_timer() in
smp_execute_task_sg() will not stop it and a UAF will happen. The process
is shown below:</p>
<p>(thread 1)               |        (thread 2)
smp_execute_task_sg()          | sas_task_internal_timedout()
 ...                           |
 del_timer()                   |
 ...                           |  ...
 sas_free_task(task)           |
  kfree(task-&amp;gt;slow_task) //FREE|
                               |  task-&amp;gt;slow_task-&amp;gt;... //USE</p>
<p>Fix by calling del_timer_sync() in smp_execute_task_sg(), which makes sure
the timer handler have finished before the &amp;quot;task-&amp;gt;slow_task&amp;quot; is
deallocated.(CVE-2022-50422)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ppp: associate skb with a device at tx</p>
<p>Syzkaller triggered flow dissector warning with the following:</p>
<p>r0 = openat$ppp(0xffffffffffffff9c, &amp;amp;(0x7f0000000000), 0xc0802, 0x0)
ioctl$PPPIOCNEWUNIT(r0, 0xc004743e, &amp;amp;(0x7f00000000c0))
ioctl$PPPIOCSACTIVE(r0, 0x40107446, &amp;amp;(0x7f0000000240)={0x2, &amp;amp;(0x7f0000000180)=[{0x20, 0x0, 0x0, 0xfffff034}, {0x6}]})
pwritev(r0, &amp;amp;(0x7f0000…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/oesa-2026-1231"/>
  </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-02T20:14:25.230761+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/rhsa-2023:7539</id>
    <title>RHSA-2023:7539 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
    <updated>2026-10-02T20:14:25.232492+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>hw: Intel: Gather Data Sampling (GDS) side channel vulnerability kernel: use-after-free due to race condition occurring in dvb_register_device() kernel: use-after-free due to race condition occurring in dvb_net.c kernel: use-after-free due to race condition occurring in dvb_ca_en50221.c kernel: Linux kernel: Memory leak in RDMA restrack leads to Denial of Service kernel: use-after-free in smb2_is_status_io_timeout() kernel: net/sched: cls_u32 component reference counter leak if tcf_change_indev() fails kernel: net/sched: Use-after-free vulnerabilities in the net/sched classifiers: cls_fw, cls_u32 and cls_route kernel: net/sched: Use-after-free vulnerabilities in the net/sched classifiers: cls_fw, cls_u32 and cls_route kernel: net/sched: Use-after-free vulnerabilities in the net/sched classifiers: cls_fw, cls_u32 and cls_route kernel: net/sched: Use-after-free vulnerabilities in the net/sched classifiers: cls_fw, cls_u32 and cls_route kernel: Race between task migrating pages and another task calling exit_mmap to release those same pages getting invalid opcode BUG in include/linux/swapops.h kernel: fbcon: out-of-sync arrays in fbcon_mode_deleted due to wrong con2fb_map assignment kernel: netfilter: potential slab-out-of-bound access due to integer underflow kernel: mm/slab_common: slab_caches list corruption after kmem_cache_destroy() kernel: i40e: Fix kernel crash during reboot when adapter is in recovery mode kernel: md/raid10: fix leak of 'r10bio-&gt;remaining' for recovery k…</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/rhsa-2023:7539"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/suse-su-2026:0263-1</id>
    <title>SUSE-SU-2026:0263-1 — Security update for the Linux Kernel</title>
    <updated>2026-10-02T20:14:25.232625+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-2026:0263-1"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ubuntu-cve-2023-53832</id>
    <title>UBUNTU-CVE-2023-53832</title>
    <updated>2026-10-02T20:14:25.233051+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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 163 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix null-ptr-deref in raid10_sync_request init_resync() inits mempool and sets conf-&gt;have_replacemnt at the beginning of sync, close_sync() frees the mempool when sync is completed. After [1] recovery might be skipped and init_resync() is called but close_sync() is not. null-ptr-deref occurs with r10bio-&gt;dev[i].repl_bio. The following is one way to reproduce the issue.   1) create a array, wait for resync to complete, mddev-&gt;recovery_cp is set      to MaxSector.   2) recovery is woken and it is skipped. conf-&gt;have_replacement is set to      0 in init_resync(). close_sync() not called.   3) some io errors and rdev A is set to WantReplacement.   4) a new device is added and set to A's replacement.   5) recovery is woken, A have replacement, but conf-&gt;have_replacemnt is      0. r10bio-&gt;dev[i].repl_bio will not be alloced and null-ptr-deref      occurs. Fix it by not calling init_resync() if recovery skipped. [1] commit 7e83ccbecd60 ("md/raid10: Allow skipping recovery when clean arrays are assembled")</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ubuntu-cve-2023-53832"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2765</id>
    <title>WID-SEC-W-2025-2765 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
    <updated>2026-10-02T20:14:25.233633+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2765"/>
  </entry>
</feed>
