<?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://db.gcve.eu</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, 19 Nov 2026 17:45:54 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21654 — ovl: support encoding fid from inode with no alias</title>
      <link>https://db.gcve.eu/vuln/cve-2025-21654</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;ovl: support encoding fid from inode with no alias&lt;/p&gt;
&lt;p&gt;Dmitry Safonov reported that a WARN_ON() assertion can be trigered by
userspace when calling inotify_show_fdinfo() for an overlayfs watched
inode, whose dentry aliases were discarded with drop_caches.&lt;/p&gt;
&lt;p&gt;The WARN_ON() assertion in inotify_show_fdinfo() was removed, because
it is possible for encoding file handle to fail for other reason, but
the impact of failing to encode an overlayfs file handle goes beyond
this assertion.&lt;/p&gt;
&lt;p&gt;As shown in the LTP test case mentioned in the link below, failure to
encode an overlayfs file handle from a non-aliased inode also leads to
failure to report an fid with FAN_DELETE_SELF fanotify events.&lt;/p&gt;
&lt;p&gt;As Dmitry notes in his analyzis of the problem, ovl_encode_fh() fails
if it cannot find an alias for the inode, but this failure can be fixed.
ovl_encode_fh() seldom uses the alias and in the case of non-decodable
file handles, as is often the case with fanotify fid info,
ovl_encode_fh() never needs to use the alias to encode a file handle.&lt;/p&gt;
&lt;p&gt;Defer finding an alias until it is actually needed so ovl_encode_fh()
will not fail in the common case of FAN_DELETE_SELF fanotify events.&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;ovl: support encoding fid from inode with no alias&lt;/p&gt;
&lt;p&gt;Dmitry Safonov reported that a WARN_ON() assertion can be trigered by
userspace when calling inotify_show_fdinfo() for an overlayfs watched
inode, whose dentry aliases were discarded with drop_caches.&lt;/p&gt;
&lt;p&gt;The WARN_ON() assertion in inotify_show_fdinfo() was removed, because
it is possible for encoding file handle to fail for other reason, but
the impact of failing to encode an overlayfs file handle goes beyond
this assertion.&lt;/p&gt;
&lt;p&gt;As shown in the LTP test case mentioned in the link below, failure to
encode an overlayfs file handle from a non-aliased inode also leads to
failure to report an fid with FAN_DELETE_SELF fanotify events.&lt;/p&gt;
&lt;p&gt;As Dmitry notes in his analyzis of the problem, ovl_encode_fh() fails
if it cannot find an alias for the inode, but this failure can be fixed.
ovl_encode_fh() seldom uses the alias and in the case of non-decodable
file handles, as is often the case with fanotify fid info,
ovl_encode_fh() never needs to use the alias to encode a file handle.&lt;/p&gt;
&lt;p&gt;Defer finding an alias until it is actually needed so ovl_encode_fh()
will not fail in the common case of FAN_DELETE_SELF fanotify events.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2025-21654</guid>
    </item>
    <item>
      <title>USN-7379-1 — linux, linux-aws, linux-azure, linux-gcp, linux-hwe-6.11, linux-oracle, linux-realtime vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-7379-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.11&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;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Drivers core;
  - Ublk userspace block driver;
  - Virtio block driver;
  - Bluetooth drivers;
  - Buffer Sharing and Synchronization framework;
  - DMA engine subsystem;
  - EFI core;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Microsoft Hyper-V drivers;
  - Hardware monitoring drivers;
  - I3C subsystem;
  - IIO ADC drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Microchip PCI driver;
  - MTD block device drivers;
  - Network drivers;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - NVME drivers;
  - PCI subsystem;
  - PHY drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - i.MX PM domains;
  - Power supply drivers;
  - Voltage and Current Regulator drivers;
  - SCSI subsystem;
  - i.MX SoC drivers;
  - SPI subsystem;
  - UFS subsystem;
  - USB Gadget drivers;
  - TDX Guest driver;
  - AFS file system;
  - BTRFS file system;
  - Ceph distributed file system;
  - File systems infrastructure;
  - F2FS file system;
  - JFFS…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.11&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;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Drivers core;
  - Ublk userspace block driver;
  - Virtio block driver;
  - Bluetooth drivers;
  - Buffer Sharing and Synchronization framework;
  - DMA engine subsystem;
  - EFI core;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Microsoft Hyper-V drivers;
  - Hardware monitoring drivers;
  - I3C subsystem;
  - IIO ADC drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Microchip PCI driver;
  - MTD block device drivers;
  - Network drivers;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - NVME drivers;
  - PCI subsystem;
  - PHY drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - i.MX PM domains;
  - Power supply drivers;
  - Voltage and Current Regulator drivers;
  - SCSI subsystem;
  - i.MX SoC drivers;
  - SPI subsystem;
  - UFS subsystem;
  - USB Gadget drivers;
  - TDX Guest driver;
  - AFS file system;
  - BTRFS file system;
  - Ceph distributed file system;
  - File systems infrastructure;
  - F2FS file system;
  - JFFS…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-7379-1</guid>
    </item>
  </channel>
</rss>
