<?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 02:11:10 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23207 — spi: tegra210-quad: Protect curr_xfer check in IRQ handler</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-23207</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;spi: tegra210-quad: Protect curr_xfer check in IRQ handler&lt;/p&gt;
&lt;p&gt;Now that all other accesses to curr_xfer are done under the lock,
protect the curr_xfer NULL check in tegra_qspi_isr_thread() with the
spinlock. Without this protection, the following race can occur:&lt;/p&gt;
&lt;p&gt;CPU0 (ISR thread)              CPU1 (timeout path)
  ----------------               -------------------
  if (!tqspi-&amp;gt;curr_xfer)
    // sees non-NULL
                                 spin_lock()
                                 tqspi-&amp;gt;curr_xfer = NULL
                                 spin_unlock()
  handle_*_xfer()
    spin_lock()
    t = tqspi-&amp;gt;curr_xfer  // NULL!
    ... t-&amp;gt;len ...        // NULL dereference!&lt;/p&gt;
&lt;p&gt;With this patch, all curr_xfer accesses are now properly synchronized.&lt;/p&gt;
&lt;p&gt;Although all accesses to curr_xfer are done under the lock, in
tegra_qspi_isr_thread() it checks for NULL, releases the lock and
reacquires it later in handle_cpu_based_xfer()/handle_dma_based_xfer().
There is a potential for an update in between, which could cause a NULL
pointer dereference.&lt;/p&gt;
&lt;p&gt;To handle this, add a NULL check inside the handlers after acquiring
the lock. This ensures that if the timeout path has already cleared
curr_xfer, the handler will safely return without dereferencing the
NULL pointer.&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;spi: tegra210-quad: Protect curr_xfer check in IRQ handler&lt;/p&gt;
&lt;p&gt;Now that all other accesses to curr_xfer are done under the lock,
protect the curr_xfer NULL check in tegra_qspi_isr_thread() with the
spinlock. Without this protection, the following race can occur:&lt;/p&gt;
&lt;p&gt;CPU0 (ISR thread)              CPU1 (timeout path)
  ----------------               -------------------
  if (!tqspi-&amp;gt;curr_xfer)
    // sees non-NULL
                                 spin_lock()
                                 tqspi-&amp;gt;curr_xfer = NULL
                                 spin_unlock()
  handle_*_xfer()
    spin_lock()
    t = tqspi-&amp;gt;curr_xfer  // NULL!
    ... t-&amp;gt;len ...        // NULL dereference!&lt;/p&gt;
&lt;p&gt;With this patch, all curr_xfer accesses are now properly synchronized.&lt;/p&gt;
&lt;p&gt;Although all accesses to curr_xfer are done under the lock, in
tegra_qspi_isr_thread() it checks for NULL, releases the lock and
reacquires it later in handle_cpu_based_xfer()/handle_dma_based_xfer().
There is a potential for an update in between, which could cause a NULL
pointer dereference.&lt;/p&gt;
&lt;p&gt;To handle this, add a NULL check inside the handlers after acquiring
the lock. This ensures that if the timeout path has already cleared
curr_xfer, the handler will safely return without dereferencing the
NULL pointer.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-23207</guid>
    </item>
    <item>
      <title>USN-8100-1 — linux-nvidia, linux-nvidia-6.8, linux-nvidia-lowlatency vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-8100-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-nvidia-6.8, Ubuntu:24.04:LTS: linux-nvidia, Ubuntu:24.04:LTS: linux-nvidia-lowlatency&lt;/p&gt;
&lt;p&gt;Qualys discovered that several vulnerabilities existed in the AppArmor
Linux kernel Security Module (LSM). An unprivileged local attacker could
use these issues to load, replace, and remove arbitrary AppArmor profiles
causing denial of service, exposure of sensitive information (kernel
memory), local privilege escalation, or possibly escape a container.
(LP: #2143853)&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;
  - MIPS architecture;
  - Nios II architecture;
  - PA-RISC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - Sun Sparc architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Xtensa architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - ATM drivers;
  - Drivers core;
  - Block device driver;
  - Network block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - Hardware random number generator core;
  - Character device driver;
  - Data acquisition framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - Device frequency scaling framework;
  - DMA engine subsystem;
  - ARM SCMI message protocol;
  - EFI core;
  - Intel Stratix 10 firmware drivers;
  - GPU drivers;
  - HID subsystem;
  - CoreSight HW tracing drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-nvidia-6.8, Ubuntu:24.04:LTS: linux-nvidia, Ubuntu:24.04:LTS: linux-nvidia-lowlatency&lt;/p&gt;
&lt;p&gt;Qualys discovered that several vulnerabilities existed in the AppArmor
Linux kernel Security Module (LSM). An unprivileged local attacker could
use these issues to load, replace, and remove arbitrary AppArmor profiles
causing denial of service, exposure of sensitive information (kernel
memory), local privilege escalation, or possibly escape a container.
(LP: #2143853)&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;
  - MIPS architecture;
  - Nios II architecture;
  - PA-RISC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - Sun Sparc architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Xtensa architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - ATM drivers;
  - Drivers core;
  - Block device driver;
  - Network block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - Hardware random number generator core;
  - Character device driver;
  - Data acquisition framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - Device frequency scaling framework;
  - DMA engine subsystem;
  - ARM SCMI message protocol;
  - EFI core;
  - Intel Stratix 10 firmware drivers;
  - GPU drivers;
  - HID subsystem;
  - CoreSight HW tracing drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-8100-1</guid>
    </item>
  </channel>
</rss>
