<?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-04T10:11:25.884914+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/cve-2026-72069</id>
    <title>CVE-2026-72069 — locking/rt: Fix the incorrect RCU protection in rt_spin_unlock()</title>
    <updated>2026-10-04T10:11:26.911774+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>locking/rt: Fix the incorrect RCU protection in rt_spin_unlock()</p>
<p>rt_spin_unlock() releases the RCU protection before unlocking the
lock. That opens the door for the following UAF scenario:</p>
<p>T1					T2
 spin_lock(&amp;p-&gt;lock);		rcu_read_lock();
 invalidate(p);			p = rcu_dereference(ptr);
 rcu_assign_pointer(ptr, NULL);	if (!p) return;
 spin_unlock(&amp;p-&gt;lock);		spin_lock(&amp;p-&gt;lock)
 				   lock(&amp;lock-&gt;lock);
				   rcu_read_lock();
 kfree_rcu(p);			rcu_read_unlock();
				....
				spin_unlock(&amp;p-&gt;lock)
				  rcu_read_unlock(); // Ends grace period
 rcu_do_batch()
   kfree(p);
			    UAF -&gt;	  rt_mutex_cmpxchg_release(&amp;lock-&gt;lock...)</p>
<p>Regular spinlocks keep preemption disabled accross the unlock operation,
which provides full RCU protection, but the RT substitution fails to
resemble that. Same applies for the rwlock substitution.</p>
<p>Move the rcu_read_unlock() invocation past the unlock operations to match
the non-RT semantics. This makes it asymmetric vs. rt_xxx_lock(), but
that's harmless as the caller needs to hold RCU read lock across the lock
operation. The migrate_enable() call stays before the unlock operation
because there is no per CPU operation in the unlock path which would
require migration to be kept disabled.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-72069"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/usn-8781-1</id>
    <title>USN-8781-1 — linux-nvidia-tegra vulnerabilities</title>
    <updated>2026-10-04T10:11:26.911945+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:24.04:LTS: linux-nvidia-tegra</p>
<p>It was discovered that some Arm processors could complete a broadcast
translation lookaside buffer (TLB) invalidation before memory writes made
through the invalidated translation were globally observed. A local
attacker could possibly use this to write to memory after permission to do
so had been revoked, bypassing memory protections or escalating privileges.
(CVE-2025-10263)</p>
<p>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;
  - User-space API (UAPI);
  - Kernel build system;
  - ARM32 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Cryptographic API;
  - Intel NPU Driver;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Drivers core;
  - DRBD Distributed Replicated Block Device drivers;
  - Rados block device (RBD) driver;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - Arm Firmware Framework for ARMv8-A(FFA);
  - EFI core;
  - FPGA Framework;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - I3C subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Input Device (Mouse) drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/usn-8781-1"/>
  </entry>
</feed>
