<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-19T23:39:49.772248+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2026-43118</id>
    <title>CVE-2026-43118 — btrfs: fix zero size inode with non-zero size after log replay</title>
    <updated>2026-11-19T23:39:49.787405+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>btrfs: fix zero size inode with non-zero size after log replay</p>
<p>When logging that an inode exists, as part of logging a new name or
logging new dir entries for a directory, we always set the generation of
the logged inode item to 0. This is to signal during log replay (in
overwrite_item()), that we should not set the i_size since we only logged
that an inode exists, so the i_size of the inode in the subvolume tree
must be preserved (as when we log new names or that an inode exists, we
don't log extents).</p>
<p>This works fine except when we have already logged an inode in full mode
or it's the first time we are logging an inode created in a past
transaction, that inode has a new i_size of 0 and then we log a new name
for the inode (due to a new hardlink or a rename), in which case we log
an i_size of 0 for the inode and a generation of 0, which causes the log
replay code to not update the inode's i_size to 0 (in overwrite_item()).</p>
<p>An example scenario:</p>
<p>mkdir /mnt/dir
  xfs_io -f -c "pwrite 0 64K" /mnt/dir/foo</p>
<p>sync</p>
<p>xfs_io -c "truncate 0" -c "fsync" /mnt/dir/foo</p>
<p>ln /mnt/dir/foo /mnt/dir/bar</p>
<p>xfs_io -c "fsync" /mnt/dir</p>
<p>&lt;power fail&gt;</p>
<p>After log replay the file remains with a size of 64K. This is because when
we first log the inode, when we fsync file foo, we log its current i_size
of 0, and then when we create a hard link we log again the inode in exists
mode (LOG_INODE_EXISTS) but we set a generatio…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-43118"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/usn-9173-1</id>
    <title>USN-9173-1 — linux, linux-aws, linux-aws-fips, linux-gcp, linux-gcp-6.8, linux-gke, linux-gkeop, linux-ibm, linux-ibm-6.8, linux-ora…</title>
    <updated>2026-11-19T23:39:49.787506+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:22.04:LTS: linux-gcp-6.8, Ubuntu:22.04:LTS: linux-ibm-6.8, Ubuntu:22.04:LTS: linux-oracle-6.8, Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-aws, Ubuntu:24.04:LTS: linux-gcp, Ubuntu:24.04:LTS: linux-gke, Ubuntu:24.04:LTS: linux-gkeop, Ubuntu:24.04:LTS: linux-ibm, Ubuntu:24.04:LTS: linux-vmware and 1 more</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:
  - Multiple devices driver;
  - eXpress Data Path;
  - Kernel build system;
  - ARM64 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Intel NPU Driver;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Drivers core;
  - Ublk userspace block driver;
  - Bus devices;
  - Hardware random number generator core;
  - Clock framework and drivers;
  - Clocksource drivers;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - Buffer Sharing and Synchronization framework;
  - DMA engine subsystem;
  - DPLL subsystem;
  - EDAC drivers;
  - FireWire subsystem;
  - Arm Firmware Framework for ARMv8-A(FFA);
  - ARM SCMI message protocol;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Microsoft Hyper-V drivers;
  - Hardware monitoring drivers;
  - CoreSight HW tracing drivers;
  - I2C subsystem;
  - I3C subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Input Device (Mouse) drivers;
  - IOMMU subsystem;
  - Media drivers;
  - MMC subsystem;
  - Network drivers;
  - Mellanox network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - STMicroelectronics network drivers;
  - Texas Instruments network drivers;
  - Ethernet tea…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/usn-9173-1"/>
  </entry>
</feed>
