<?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 19:26:40 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38492 — netfs: Fix race between cache write completion and ALL_QUEUED being set</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-38492</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;netfs: Fix race between cache write completion and ALL_QUEUED being set&lt;/p&gt;
&lt;p&gt;When netfslib is issuing subrequests, the subrequests start processing
immediately and may complete before we reach the end of the issuing
function.  At the end of the issuing function we set NETFS_RREQ_ALL_QUEUED
to indicate to the collector that we aren&amp;#39;t going to issue any more subreqs
and that it can do the final notifications and cleanup.&lt;/p&gt;
&lt;p&gt;Now, this isn&amp;#39;t a problem if the request is synchronous
(NETFS_RREQ_OFFLOAD_COLLECTION is unset) as the result collection will be
done in-thread and we&amp;#39;re guaranteed an opportunity to run the collector.&lt;/p&gt;
&lt;p&gt;However, if the request is asynchronous, collection is primarily triggered
by the termination of subrequests queuing it on a workqueue.  Now, a race
can occur here if the app thread sets ALL_QUEUED after the last subrequest
terminates.&lt;/p&gt;
&lt;p&gt;This can happen most easily with the copy2cache code (as used by Ceph)
where, in the collection routine of a read request, an asynchronous write
request is spawned to copy data to the cache.  Folios are added to the
write request as they&amp;#39;re unlocked, but there may be a delay before
ALL_QUEUED is set as the write subrequests may complete before we get
there.&lt;/p&gt;
&lt;p&gt;If all the write subreqs have finished by the ALL_QUEUED point, no further
events happen and the collection never happens, leaving the request
hanging.&lt;/p&gt;
&lt;p&gt;Fix this by queuing the collector after setting ALL_QUE…&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;netfs: Fix race between cache write completion and ALL_QUEUED being set&lt;/p&gt;
&lt;p&gt;When netfslib is issuing subrequests, the subrequests start processing
immediately and may complete before we reach the end of the issuing
function.  At the end of the issuing function we set NETFS_RREQ_ALL_QUEUED
to indicate to the collector that we aren&amp;#39;t going to issue any more subreqs
and that it can do the final notifications and cleanup.&lt;/p&gt;
&lt;p&gt;Now, this isn&amp;#39;t a problem if the request is synchronous
(NETFS_RREQ_OFFLOAD_COLLECTION is unset) as the result collection will be
done in-thread and we&amp;#39;re guaranteed an opportunity to run the collector.&lt;/p&gt;
&lt;p&gt;However, if the request is asynchronous, collection is primarily triggered
by the termination of subrequests queuing it on a workqueue.  Now, a race
can occur here if the app thread sets ALL_QUEUED after the last subrequest
terminates.&lt;/p&gt;
&lt;p&gt;This can happen most easily with the copy2cache code (as used by Ceph)
where, in the collection routine of a read request, an asynchronous write
request is spawned to copy data to the cache.  Folios are added to the
write request as they&amp;#39;re unlocked, but there may be a delay before
ALL_QUEUED is set as the write subrequests may complete before we get
there.&lt;/p&gt;
&lt;p&gt;If all the write subreqs have finished by the ALL_QUEUED point, no further
events happen and the collection never happens, leaving the request
hanging.&lt;/p&gt;
&lt;p&gt;Fix this by queuing the collector after setting ALL_QUE…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-38492</guid>
    </item>
    <item>
      <title>USN-7879-1 — linux, linux-aws, linux-gcp, linux-hwe-6.14, linux-oracle, linux-realtime vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-7879-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.14&lt;/p&gt;
&lt;p&gt;It was discovered that improper initialization of CPU cache memory could
allow a local attacker with hypervisor access to overwrite SEV-SNP guest
memory resulting in loss of data integrity. (CVE-2024-36331)&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;
  - PowerPC architecture;
  - S390 architecture;
  - x86 architecture;
  - Network block device driver;
  - Character device driver;
  - Clock framework and drivers;
  - Data acquisition framework and drivers;
  - Hardware crypto device drivers;
  - Device frequency scaling framework;
  - DMA engine subsystem;
  - EDAC drivers;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - IIO subsystem;
  - IIO ADC drivers;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Multiple devices driver;
  - Media drivers;
  - Network drivers;
  - Mellanox network drivers;
  - PCI subsystem;
  - PHY drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - Power supply drivers;
  - Powercap sysfs driver;
  - Voltage and Current Regulator drivers;
  - S/390 drivers;
  - ASPEED SoC drivers;
  - SPI subsystem;
  - small TFT LCD display modules;
  - Media staging drivers;
  - USB Gadget drivers;
  - vDPA drivers;
  - VFIO drivers;
  - Framebuffer layer;
  - Xen hypervisor drivers;
  - BTRFS file system;
  - Ceph distributed file sy…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.14&lt;/p&gt;
&lt;p&gt;It was discovered that improper initialization of CPU cache memory could
allow a local attacker with hypervisor access to overwrite SEV-SNP guest
memory resulting in loss of data integrity. (CVE-2024-36331)&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;
  - PowerPC architecture;
  - S390 architecture;
  - x86 architecture;
  - Network block device driver;
  - Character device driver;
  - Clock framework and drivers;
  - Data acquisition framework and drivers;
  - Hardware crypto device drivers;
  - Device frequency scaling framework;
  - DMA engine subsystem;
  - EDAC drivers;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - IIO subsystem;
  - IIO ADC drivers;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Multiple devices driver;
  - Media drivers;
  - Network drivers;
  - Mellanox network drivers;
  - PCI subsystem;
  - PHY drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - Power supply drivers;
  - Powercap sysfs driver;
  - Voltage and Current Regulator drivers;
  - S/390 drivers;
  - ASPEED SoC drivers;
  - SPI subsystem;
  - small TFT LCD display modules;
  - Media staging drivers;
  - USB Gadget drivers;
  - vDPA drivers;
  - VFIO drivers;
  - Framebuffer layer;
  - Xen hypervisor drivers;
  - BTRFS file system;
  - Ceph distributed file sy…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-7879-1</guid>
    </item>
  </channel>
</rss>
