<?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>Thu, 15 Oct 2026 12:28:09 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21684 — gpio: xilinx: Convert gpio_lock to raw spinlock</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-21684</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;gpio: xilinx: Convert gpio_lock to raw spinlock&lt;/p&gt;
&lt;p&gt;irq_chip functions may be called in raw spinlock context. Therefore, we
must also use a raw spinlock for our own internal locking.&lt;/p&gt;
&lt;p&gt;This fixes the following lockdep splat:&lt;/p&gt;
&lt;p&gt;[    5.349336] =============================
[    5.353349] [ BUG: Invalid wait context ]
[    5.357361] 6.13.0-rc5+ #69 Tainted: G        W
[    5.363031] -----------------------------
[    5.367045] kworker/u17:1/44 is trying to lock:
[    5.371587] ffffff88018b02c0 (&amp;amp;chip-&amp;gt;gpio_lock){....}-{3:3}, at: xgpio_irq_unmask (drivers/gpio/gpio-xilinx.c:433 (discriminator 8))
[    5.380079] other info that might help us debug this:
[    5.385138] context-{5:5}
[    5.387762] 5 locks held by kworker/u17:1/44:
[    5.392123] #0: ffffff8800014958 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work (kernel/workqueue.c:3204)
[    5.402260] #1: ffffffc082fcbdd8 (deferred_probe_work){+.+.}-{0:0}, at: process_one_work (kernel/workqueue.c:3205)
[    5.411528] #2: ffffff880172c900 (&amp;amp;dev-&amp;gt;mutex){....}-{4:4}, at: __device_attach (drivers/base/dd.c:1006)
[    5.419929] #3: ffffff88039c8268 (request_class#2){+.+.}-{4:4}, at: __setup_irq (kernel/irq/internals.h:156 kernel/irq/manage.c:1596)
[    5.428331] #4: ffffff88039c80c8 (lock_class#2){....}-{2:2}, at: __setup_irq (kernel/irq/manage.c:1614)
[    5.436472] stack backtrace:
[    5.439359] CPU: 2 UID: 0 PID: 44 Comm: kworker/u17:1 Tainted: G…&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;gpio: xilinx: Convert gpio_lock to raw spinlock&lt;/p&gt;
&lt;p&gt;irq_chip functions may be called in raw spinlock context. Therefore, we
must also use a raw spinlock for our own internal locking.&lt;/p&gt;
&lt;p&gt;This fixes the following lockdep splat:&lt;/p&gt;
&lt;p&gt;[    5.349336] =============================
[    5.353349] [ BUG: Invalid wait context ]
[    5.357361] 6.13.0-rc5+ #69 Tainted: G        W
[    5.363031] -----------------------------
[    5.367045] kworker/u17:1/44 is trying to lock:
[    5.371587] ffffff88018b02c0 (&amp;amp;chip-&amp;gt;gpio_lock){....}-{3:3}, at: xgpio_irq_unmask (drivers/gpio/gpio-xilinx.c:433 (discriminator 8))
[    5.380079] other info that might help us debug this:
[    5.385138] context-{5:5}
[    5.387762] 5 locks held by kworker/u17:1/44:
[    5.392123] #0: ffffff8800014958 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work (kernel/workqueue.c:3204)
[    5.402260] #1: ffffffc082fcbdd8 (deferred_probe_work){+.+.}-{0:0}, at: process_one_work (kernel/workqueue.c:3205)
[    5.411528] #2: ffffff880172c900 (&amp;amp;dev-&amp;gt;mutex){....}-{4:4}, at: __device_attach (drivers/base/dd.c:1006)
[    5.419929] #3: ffffff88039c8268 (request_class#2){+.+.}-{4:4}, at: __setup_irq (kernel/irq/internals.h:156 kernel/irq/manage.c:1596)
[    5.428331] #4: ffffff88039c80c8 (lock_class#2){....}-{2:2}, at: __setup_irq (kernel/irq/manage.c:1614)
[    5.436472] stack backtrace:
[    5.439359] CPU: 2 UID: 0 PID: 44 Comm: kworker/u17:1 Tainted: G…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-21684</guid>
    </item>
    <item>
      <title>USN-7445-1 — linux, linux-aws, linux-gcp, linux-hwe-6.11, linux-lowlatency, linux-lowlatency-hwe-6.11, linux-oem-6.11, linux-oracle,…</title>
      <link>https://cve.radiocsirt.org/vuln/usn-7445-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.11, Ubuntu:24.04:LTS: linux-lowlatency-hwe-6.11, Ubuntu:24.04:LTS: linux-oem-6.11&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:
  - GPIO subsystem;
  - GPU drivers;
  - IRQ chip drivers;
  - Network drivers;
  - Mellanox network drivers;
  - x86 platform drivers;
  - i.MX PM domains;
  - SCSI subsystem;
  - USB Serial drivers;
  - AFS file system;
  - GFS2 file system;
  - File systems infrastructure;
  - Proc file system;
  - SMB network file system;
  - Timer subsystem;
  - Kernel CPU control infrastructure;
  - Memory management;
  - Networking core;
  - Ethtool driver;
  - IEEE 802.15.4 subsystem;
  - Open vSwitch;
  - Network traffic control;
  - VMware vSockets driver;
(CVE-2025-21685, CVE-2025-21684, CVE-2025-21756, CVE-2025-21670,
CVE-2024-57949, CVE-2025-21677, CVE-2025-21680, CVE-2025-21703,
CVE-2024-57952, CVE-2025-21674, CVE-2025-21701, CVE-2025-21691,
CVE-2025-21689, CVE-2025-21668, CVE-2025-21665, CVE-2025-21683,
CVE-2025-21675, CVE-2025-21672, CVE-2024-57948, CVE-2025-21669,
CVE-2025-21673, CVE-2025-21692, CVE-2025-21699, CVE-2025-21702,
CVE-2025-21682, CVE-2025-21690, CVE-2025-21681, CVE-2025-21695,
CVE-2025-21696, CVE-2025-21700, CVE-2025-21678, CVE-2025-21676,
CVE-2024-57950, CVE-2025-21666, CVE-2025-21694, CVE-2025-21693,
CVE-2025-21993, CVE-2024-57951, CVE-2025-21697, CVE-2025-21667)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.11, Ubuntu:24.04:LTS: linux-lowlatency-hwe-6.11, Ubuntu:24.04:LTS: linux-oem-6.11&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:
  - GPIO subsystem;
  - GPU drivers;
  - IRQ chip drivers;
  - Network drivers;
  - Mellanox network drivers;
  - x86 platform drivers;
  - i.MX PM domains;
  - SCSI subsystem;
  - USB Serial drivers;
  - AFS file system;
  - GFS2 file system;
  - File systems infrastructure;
  - Proc file system;
  - SMB network file system;
  - Timer subsystem;
  - Kernel CPU control infrastructure;
  - Memory management;
  - Networking core;
  - Ethtool driver;
  - IEEE 802.15.4 subsystem;
  - Open vSwitch;
  - Network traffic control;
  - VMware vSockets driver;
(CVE-2025-21685, CVE-2025-21684, CVE-2025-21756, CVE-2025-21670,
CVE-2024-57949, CVE-2025-21677, CVE-2025-21680, CVE-2025-21703,
CVE-2024-57952, CVE-2025-21674, CVE-2025-21701, CVE-2025-21691,
CVE-2025-21689, CVE-2025-21668, CVE-2025-21665, CVE-2025-21683,
CVE-2025-21675, CVE-2025-21672, CVE-2024-57948, CVE-2025-21669,
CVE-2025-21673, CVE-2025-21692, CVE-2025-21699, CVE-2025-21702,
CVE-2025-21682, CVE-2025-21690, CVE-2025-21681, CVE-2025-21695,
CVE-2025-21696, CVE-2025-21700, CVE-2025-21678, CVE-2025-21676,
CVE-2024-57950, CVE-2025-21666, CVE-2025-21694, CVE-2025-21693,
CVE-2025-21993, CVE-2024-57951, CVE-2025-21697, CVE-2025-21667)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-7445-1</guid>
    </item>
  </channel>
</rss>
