<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-05T16:24:16.332332+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/bdu:2026-11421</id>
    <title>bdu:2026-11421</title>
    <updated>2026-10-05T16:24:16.449755+00:00</updated>
    <content>bdu:2026-11421</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2026-11421"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2025-68282</id>
    <title>BELL-CVE-2025-68282</title>
    <updated>2026-10-05T16:24:16.449810+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2025-68282"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0057</id>
    <title>certfr-2026-avi-0057 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
    <updated>2026-10-05T16:24:16.449855+00:00</updated>
    <content>certfr-2026-avi-0057</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-0057"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-315088</id>
    <title>EUVD-2026-315088</title>
    <updated>2026-10-05T16:24:16.449882+00:00</updated>
    <content>EUVD-2026-315088</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-315088"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-68282</id>
    <title>fkie_cve-2025-68282</title>
    <updated>2026-10-05T16:24:16.449903+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>usb: gadget: udc: fix use-after-free in usb_gadget_state_work</p>
<p>A race condition during gadget teardown can lead to a use-after-free
in usb_gadget_state_work(), as reported by KASAN:</p>
<p>BUG: KASAN: invalid-access in sysfs_notify+0x2c/0xd0
  Workqueue: events usb_gadget_state_work</p>
<p>The fundamental race occurs because a concurrent event (e.g., an
interrupt) can call usb_gadget_set_state() and schedule gadget-&gt;work
at any time during the cleanup process in usb_del_gadget().</p>
<p>Commit 399a45e5237c ("usb: gadget: core: flush gadget workqueue after
device removal") attempted to fix this by moving flush_work() to after
device_del(). However, this does not fully solve the race, as a new
work item can still be scheduled *after* flush_work() completes but
before the gadget's memory is freed, leading to the same use-after-free.</p>
<p>This patch fixes the race condition robustly by introducing a 'teardown'
flag and a 'state_lock' spinlock to the usb_gadget struct. The flag is
set during cleanup in usb_del_gadget() *before* calling flush_work() to
prevent any new work from being scheduled once cleanup has commenced.
The scheduling site, usb_gadget_set_state(), now checks this flag under
the lock before queueing the work, thus safely closing the race window.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-68282"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-8p7c-4hwq-mwgw</id>
    <title>GHSA-8p7c-4hwq-mwgw</title>
    <updated>2026-10-05T16:24:16.449961+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>usb: gadget: udc: fix use-after-free in usb_gadget_state_work</p>
<p>A race condition during gadget teardown can lead to a use-after-free
in usb_gadget_state_work(), as reported by KASAN:</p>
<p>BUG: KASAN: invalid-access in sysfs_notify+0x2c/0xd0
  Workqueue: events usb_gadget_state_work</p>
<p>The fundamental race occurs because a concurrent event (e.g., an
interrupt) can call usb_gadget_set_state() and schedule gadget-&gt;work
at any time during the cleanup process in usb_del_gadget().</p>
<p>Commit 399a45e5237c ("usb: gadget: core: flush gadget workqueue after
device removal") attempted to fix this by moving flush_work() to after
device_del(). However, this does not fully solve the race, as a new
work item can still be scheduled *after* flush_work() completes but
before the gadget's memory is freed, leading to the same use-after-free.</p>
<p>This patch fixes the race condition robustly by introducing a 'teardown'
flag and a 'state_lock' spinlock to the usb_gadget struct. The flag is
set during cleanup in usb_del_gadget() *before* calling flush_work() to
prevent any new work from being scheduled once cleanup has commenced.
The scheduling site, usb_gadget_set_state(), now checks this flag under
the lock before queueing the work, thus safely closing the race window.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-8p7c-4hwq-mwgw"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2025-68282</id>
    <title>msrc_CVE-2025-68282 — usb: gadget: udc: fix use-after-free in usb_gadget_state_work</title>
    <updated>2026-10-05T16:24:16.450009+00:00</updated>
    <content>msrc_CVE-2025-68282</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2025-68282"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2026-1566</id>
    <title>OESA-2026-1566 — kernel security update</title>
    <updated>2026-10-05T16:24:16.450036+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:24.03-LTS-SP1: 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>udp: Deal with race between UDP socket address change and rehash</p>
<p>If a UDP socket changes its local address while it&amp;apos;s receiving
datagrams, as a result of connect(), there is a period during which
a lookup operation might fail to find it, after the address is changed
but before the secondary hash (port and address) and the four-tuple
hash (local and remote ports and addresses) are updated.</p>
<p>Secondary hash chains were introduced by commit 30fff9231fad (&amp;quot;udp:
bind() optimisation&amp;quot;) and, as a result, a rehash operation became
needed to make a bound socket reachable again after a connect().</p>
<p>This operation was introduced by commit 719f835853a9 (&amp;quot;udp: add
rehash on connect()&amp;quot;) which isn&amp;apos;t however a complete fix: the
socket will be found once the rehashing completes, but not while
it&amp;apos;s pending.</p>
<p>This is noticeable with a socat(1) server in UDP4-LISTEN mode, and a
client sending datagrams to it. After the server receives the first
datagram (cf. _xioopen_ipdgram_listen()), it issues a connect() to
the address of the sender, in order to set up a directed flow.</p>
<p>Now, if the client, running on a different CPU thread, happens to
send a (subsequent) datagram while the server&amp;apos;s socket changes its
address, but is not rehashed yet, this will result in a failed
lookup and a port unreachable error delivered to the…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2026-1566"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-68282</id>
    <title>UBUNTU-CVE-2025-68282</title>
    <updated>2026-10-05T16:24:16.450710+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 231 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: usb: gadget: udc: fix use-after-free in usb_gadget_state_work A race condition during gadget teardown can lead to a use-after-free in usb_gadget_state_work(), as reported by KASAN:   BUG: KASAN: invalid-access in sysfs_notify+0x2c/0xd0   Workqueue: events usb_gadget_state_work The fundamental race occurs because a concurrent event (e.g., an interrupt) can call usb_gadget_set_state() and schedule gadget-&gt;work at any time during the cleanup process in usb_del_gadget(). Commit 399a45e5237c ("usb: gadget: core: flush gadget workqueue after device removal") attempted to fix this by moving flush_work() to after device_del(). However, this does not fully solve the race, as a new work item can still be scheduled *after* flush_work() completes but before the gadget's memory is freed, leading to the same use-after-free. This patch fixes the race condition robustly by introducing a 'teardown' flag and a 'state_lock' spinlock to the usb_gadget struct. The flag is set during cleanup in usb_del_gadget() *before* calling flush_work() to prevent any new work from being scheduled once cleanup has commenced. The scheduling site, usb_gadget_set_state(), now checks this flag under the lock before queueing the work, thus safely closing the race window.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-68282"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2868</id>
    <title>WID-SEC-W-2025-2868 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-10-05T16:24:16.451182+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 nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2868"/>
  </entry>
</feed>
