<?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://cve.radiocsirt.org</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, 16 Oct 2026 23:02:05 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31667 — Input: uinput - fix circular locking dependency with ff-core</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-31667</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Input: uinput - fix circular locking dependency with ff-core&lt;/p&gt;
&lt;p&gt;A lockdep circular locking dependency warning can be triggered
reproducibly when using a force-feedback gamepad with uinput (for
example, playing ELDEN RING under Wine with a Flydigi Vader 5
controller):&lt;/p&gt;
&lt;p&gt;ff-&amp;gt;mutex -&amp;gt; udev-&amp;gt;mutex -&amp;gt; input_mutex -&amp;gt; dev-&amp;gt;mutex -&amp;gt; ff-&amp;gt;mutex&lt;/p&gt;
&lt;p&gt;The cycle is caused by four lock acquisition paths:&lt;/p&gt;
&lt;p&gt;1. ff upload: input_ff_upload() holds ff-&amp;gt;mutex and calls
   uinput_dev_upload_effect() -&amp;gt; uinput_request_submit() -&amp;gt;
   uinput_request_send(), which acquires udev-&amp;gt;mutex.&lt;/p&gt;
&lt;p&gt;2. device create: uinput_ioctl_handler() holds udev-&amp;gt;mutex and calls
   uinput_create_device() -&amp;gt; input_register_device(), which acquires
   input_mutex.&lt;/p&gt;
&lt;p&gt;3. device register: input_register_device() holds input_mutex and
   calls kbd_connect() -&amp;gt; input_register_handle(), which acquires
   dev-&amp;gt;mutex.&lt;/p&gt;
&lt;p&gt;4. evdev release: evdev_release() calls input_flush_device() under
   dev-&amp;gt;mutex, which calls input_ff_flush() acquiring ff-&amp;gt;mutex.&lt;/p&gt;
&lt;p&gt;Fix this by introducing a new state_lock spinlock to protect
udev-&amp;gt;state and udev-&amp;gt;dev access in uinput_request_send() instead of
acquiring udev-&amp;gt;mutex.  The function only needs to atomically check
device state and queue an input event into the ring buffer via
uinput_dev_event() -- both operations are safe under a spinlock
(ktime_get_ts64() and wake_up_interruptible() do not sleep).  This
breaks the ff-&amp;gt;mutex -&amp;gt; udev-&amp;gt;mutex lin…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Input: uinput - fix circular locking dependency with ff-core&lt;/p&gt;
&lt;p&gt;A lockdep circular locking dependency warning can be triggered
reproducibly when using a force-feedback gamepad with uinput (for
example, playing ELDEN RING under Wine with a Flydigi Vader 5
controller):&lt;/p&gt;
&lt;p&gt;ff-&amp;gt;mutex -&amp;gt; udev-&amp;gt;mutex -&amp;gt; input_mutex -&amp;gt; dev-&amp;gt;mutex -&amp;gt; ff-&amp;gt;mutex&lt;/p&gt;
&lt;p&gt;The cycle is caused by four lock acquisition paths:&lt;/p&gt;
&lt;p&gt;1. ff upload: input_ff_upload() holds ff-&amp;gt;mutex and calls
   uinput_dev_upload_effect() -&amp;gt; uinput_request_submit() -&amp;gt;
   uinput_request_send(), which acquires udev-&amp;gt;mutex.&lt;/p&gt;
&lt;p&gt;2. device create: uinput_ioctl_handler() holds udev-&amp;gt;mutex and calls
   uinput_create_device() -&amp;gt; input_register_device(), which acquires
   input_mutex.&lt;/p&gt;
&lt;p&gt;3. device register: input_register_device() holds input_mutex and
   calls kbd_connect() -&amp;gt; input_register_handle(), which acquires
   dev-&amp;gt;mutex.&lt;/p&gt;
&lt;p&gt;4. evdev release: evdev_release() calls input_flush_device() under
   dev-&amp;gt;mutex, which calls input_ff_flush() acquiring ff-&amp;gt;mutex.&lt;/p&gt;
&lt;p&gt;Fix this by introducing a new state_lock spinlock to protect
udev-&amp;gt;state and udev-&amp;gt;dev access in uinput_request_send() instead of
acquiring udev-&amp;gt;mutex.  The function only needs to atomically check
device state and queue an input event into the ring buffer via
uinput_dev_event() -- both operations are safe under a spinlock
(ktime_get_ts64() and wake_up_interruptible() do not sleep).  This
breaks the ff-&amp;gt;mutex -&amp;gt; udev-&amp;gt;mutex lin…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-31667</guid>
    </item>
    <item>
      <title>USN-8567-1 — linux, linux-gcp, linux-gcp-6.8, linux-gke, linux-gkeop, linux-realtime, linux-realtime-6.8 vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-8567-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-gcp-6.8, Ubuntu:Pro:Realtime:22.04:LTS: linux-realtime-6.8, Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-gcp, Ubuntu:24.04:LTS: linux-gke, Ubuntu:24.04:LTS: linux-gkeop, Ubuntu:Pro:Realtime:24.04:LTS: linux-realtime&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD processors did not properly clear data in
the floating point divider unit during speculative execution. A local
attacker could use this to expose sensitive information. (CVE-2025-54505)&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD Zen 2 processors did not properly isolate
shared resources in the operation cache. A local attacker could possibly
use this issue to corrupt instructions executed at a higher privilege
level, resulting in privilege escalation. (CVE-2025-54518)&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD Zen 5 processors supporting RDSEED
instruction did not properly handle entropy, potentially resulting in the
consumption of insufficiently random values. A local attacker could
possibly use this issue to influence the values returned by the RDSEED
instruction causing loss of confidentiality and integrity. (CVE-2025-62626)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - Power management core;
  - DRBD Distributed Replicated Block Device drivers;
  - Rados block device (RBD) driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - Charact…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-gcp-6.8, Ubuntu:Pro:Realtime:22.04:LTS: linux-realtime-6.8, Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-gcp, Ubuntu:24.04:LTS: linux-gke, Ubuntu:24.04:LTS: linux-gkeop, Ubuntu:Pro:Realtime:24.04:LTS: linux-realtime&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD processors did not properly clear data in
the floating point divider unit during speculative execution. A local
attacker could use this to expose sensitive information. (CVE-2025-54505)&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD Zen 2 processors did not properly isolate
shared resources in the operation cache. A local attacker could possibly
use this issue to corrupt instructions executed at a higher privilege
level, resulting in privilege escalation. (CVE-2025-54518)&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD Zen 5 processors supporting RDSEED
instruction did not properly handle entropy, potentially resulting in the
consumption of insufficiently random values. A local attacker could
possibly use this issue to influence the values returned by the RDSEED
instruction causing loss of confidentiality and integrity. (CVE-2025-62626)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - Power management core;
  - DRBD Distributed Replicated Block Device drivers;
  - Rados block device (RBD) driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - Charact…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-8567-1</guid>
    </item>
  </channel>
</rss>
