<?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>Wed, 14 Oct 2026 15:16:14 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64265 — fuse: clear intr_entry in fuse_resend and fuse_remove_pending_req</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-64265</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;fuse: clear intr_entry in fuse_resend and fuse_remove_pending_req&lt;/p&gt;
&lt;p&gt;When fuse_resend() moves a request from fpq-&amp;gt;processing back to
fiq-&amp;gt;pending, it sets FR_PENDING and clears FR_SENT but does not
remove the requests intr_entry from fiq-&amp;gt;interrupts.  If the
request had FR_INTERRUPTED set from a prior signal, intr_entry
remains dangling on fiq-&amp;gt;interrupts.  When the requesting task
then receives a fatal signal, fuse_remove_pending_req() sees
FR_PENDING=1, removes the request from fiq-&amp;gt;pending and frees it
via the refcount path, also without cleaning intr_entry.  The
stale intr_entry causes use-after-free when fuse_read_interrupt()
iterates fiq-&amp;gt;interrupts:
  - list_del_init(&amp;amp;req-&amp;gt;intr_entry) -&amp;gt; UAF write on freed slab
  - req-&amp;gt;in.h.unique -&amp;gt; UAF read, data leaked to userspace&lt;/p&gt;
&lt;p&gt;Remove intr_entry from fiq-&amp;gt;interrupts in fuse_resend() for
interrupted requests before they are placed back on fiq-&amp;gt;pending.&lt;/p&gt;
&lt;p&gt;Add a WARN_ON if the intr_entry is not empty on request destruction.&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;fuse: clear intr_entry in fuse_resend and fuse_remove_pending_req&lt;/p&gt;
&lt;p&gt;When fuse_resend() moves a request from fpq-&amp;gt;processing back to
fiq-&amp;gt;pending, it sets FR_PENDING and clears FR_SENT but does not
remove the requests intr_entry from fiq-&amp;gt;interrupts.  If the
request had FR_INTERRUPTED set from a prior signal, intr_entry
remains dangling on fiq-&amp;gt;interrupts.  When the requesting task
then receives a fatal signal, fuse_remove_pending_req() sees
FR_PENDING=1, removes the request from fiq-&amp;gt;pending and frees it
via the refcount path, also without cleaning intr_entry.  The
stale intr_entry causes use-after-free when fuse_read_interrupt()
iterates fiq-&amp;gt;interrupts:
  - list_del_init(&amp;amp;req-&amp;gt;intr_entry) -&amp;gt; UAF write on freed slab
  - req-&amp;gt;in.h.unique -&amp;gt; UAF read, data leaked to userspace&lt;/p&gt;
&lt;p&gt;Remove intr_entry from fiq-&amp;gt;interrupts in fuse_resend() for
interrupted requests before they are placed back on fiq-&amp;gt;pending.&lt;/p&gt;
&lt;p&gt;Add a WARN_ON if the intr_entry is not empty on request destruction.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-64265</guid>
    </item>
    <item>
      <title>USN-8726-1 — linux, linux-aws, linux-aws-7.0, linux-gcp, linux-gke, linux-hwe-7.0, linux-realtime vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-8726-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-aws-7.0, Ubuntu:24.04:LTS: linux-hwe-7.0, Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-gke, Ubuntu:26.04:LTS: linux-realtime&lt;/p&gt;
&lt;p&gt;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)&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;
  - User-space API (UAPI);
  - Kernel build system;
  - ARM32 architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - Intel NPU Driver;
  - ACPI drivers;
  - Android drivers;
  - Drivers core;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - Character device driver;
  - Hardware random number generator core;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - Buffer Sharing and Synchronization framework;
  - Intel Stratix 10 firmware drivers;
  - FPGA Framework;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - CoreSight HW tracing drivers;
  - I2C subsystem;
  - IIO subsystem;
  - IIO ADC drivers;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Input Device (Mouse) drivers;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - M…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-aws-7.0, Ubuntu:24.04:LTS: linux-hwe-7.0, Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-gke, Ubuntu:26.04:LTS: linux-realtime&lt;/p&gt;
&lt;p&gt;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)&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;
  - User-space API (UAPI);
  - Kernel build system;
  - ARM32 architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - Intel NPU Driver;
  - ACPI drivers;
  - Android drivers;
  - Drivers core;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - Character device driver;
  - Hardware random number generator core;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - Buffer Sharing and Synchronization framework;
  - Intel Stratix 10 firmware drivers;
  - FPGA Framework;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - CoreSight HW tracing drivers;
  - I2C subsystem;
  - IIO subsystem;
  - IIO ADC drivers;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Input Device (Mouse) drivers;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - M…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-8726-1</guid>
    </item>
  </channel>
</rss>
