<?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-01T15:18:24.455943+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-2025-71099</id>
    <title>CVE-2025-71099 — drm/xe/oa: Fix potential UAF in xe_oa_add_config_ioctl()</title>
    <updated>2026-10-01T15:18:25.304523+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>drm/xe/oa: Fix potential UAF in xe_oa_add_config_ioctl()</p>
<p>In xe_oa_add_config_ioctl(), we accessed oa_config-&gt;id after dropping
metrics_lock. Since this lock protects the lifetime of oa_config, an
attacker could guess the id and call xe_oa_remove_config_ioctl() with
perfect timing, freeing oa_config before we dereference it, leading to
a potential use-after-free.</p>
<p>Fix this by caching the id in a local variable while holding the lock.</p>
<p>v2: (Matt A)
- Dropped mutex_unlock(&amp;oa-&gt;metrics_lock) ordering change from
  xe_oa_remove_config_ioctl()</p>
<p>(cherry picked from commit 28aeaed130e8e587fd1b73b6d66ca41ccc5a1a31)</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-71099"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/usn-8177-1</id>
    <title>USN-8177-1 — linux, linux-realtime vulnerabilities</title>
    <updated>2026-10-01T15:18:25.304675+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:25.10: linux, Ubuntu:25.10: linux-realtime</p>
<p>Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo
Rizzo discovered that some AMD Zen processors did not properly verify the
signature of CPU microcode. This flaw is known as EntrySign. A privileged
attacker could possibly use this issue to cause load malicious CPU
microcode causing loss of integrity and confidentiality.
(CVE-2024-36347)</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:
  - MIPS architecture;
  - PowerPC architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - ACPI drivers;
  - Ublk userspace block driver;
  - Bluetooth drivers;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - GPU drivers;
  - Hardware monitoring drivers;
  - Intel Trace Hub HW tracing drivers;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Input Device (Mouse) drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Network drivers;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - Ethernet team driver;
  - PA-RISC drivers;
  - Chrome hardware platform drivers;
  - x86 platform drivers;
  - SCSI subsystem;
  - SPI subsystem;
  - TCM subsystem;
  - Freescale USB OTG Transceiver Driver;
  - USB Type-C Connector System Software Interface driver;
  - Watchdog drivers;
  - BTRFS file sy…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/usn-8177-1"/>
  </entry>
</feed>
