<?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-19T17:18:17.496761+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-2025-68778</id>
    <title>CVE-2025-68778 — btrfs: don't log conflicting inode if it's a dir moved in the current transaction</title>
    <updated>2026-11-19T17:18:17.515937+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: don't log conflicting inode if it's a dir moved in the current transaction</p>
<p>We can't log a conflicting inode if it's a directory and it was moved
from one parent directory to another parent directory in the current
transaction, as this can result an attempt to have a directory with
two hard links during log replay, one for the old parent directory and
another for the new parent directory.</p>
<p>The following scenario triggers that issue:</p>
<p>1) We have directories "dir1" and "dir2" created in a past transaction.
   Directory "dir1" has inode A as its parent directory;</p>
<p>2) We move "dir1" to some other directory;</p>
<p>3) We create a file with the name "dir1" in directory inode A;</p>
<p>4) We fsync the new file. This results in logging the inode of the new file
   and the inode for the directory "dir1" that was previously moved in the
   current transaction. So the log tree has the INODE_REF item for the
   new location of "dir1";</p>
<p>5) We move the new file to some other directory. This results in updating
   the log tree to included the new INODE_REF for the new location of the
   file and removes the INODE_REF for the old location. This happens
   during the rename when we call btrfs_log_new_name();</p>
<p>6) We fsync the file, and that persists the log tree changes done in the
   previous step (btrfs_log_new_name() only updates the log tree in
   memory);</p>
<p>7) We have a power failure;</p>
<p>8) Next time the fs is mounted, log repl…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2025-68778"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/usn-8177-1</id>
    <title>USN-8177-1 — linux, linux-realtime vulnerabilities</title>
    <updated>2026-11-19T17:18:17.516047+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://db.gcve.eu/vuln/usn-8177-1"/>
  </entry>
</feed>
