Vulnerabilities

Vulnerability · CVE-2025-68778

In the Linux kernel, the following vulnerability has been resolved: btrfs: don't log conflicting inode if it's a dir moved in the current transaction We can't log a conflicting ino

Published Jan 13, 2026 · catalog updated May 11, 2026 · Linux Linux

Last checked Nov 4, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2025-68778. EPSS is 0.20%. Act only if a listed version of Linux Linux is installed.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
None0.0
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.20%
Remediation
Version ranges on file
Affected products
vendor Linux Linux 44f714dae50a2e795d3268a6831762aa6fa54f55 <a35788ddf8df65837897ecbb0ddb2896b863159e

In the Linux kernel, the following vulnerability has been resolved: btrfs: don't log conflicting inode if it's a dir moved in the current transaction 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. The following scenario triggers that issue: 1) We have directories "dir1" and "dir2" created in a past transaction. Directory "dir1" h

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor Linux Linux 44f714dae50a2e795d3268a6831762aa6fa54f55 <a35788ddf8df65837897ecbb0ddb2896b863159e44f714dae50a2e795d3268a6831762aa6fa54f55 <a35788ddf8df65837897ecbb0ddb2896b863159e

How to fix CVE-2025-68778

  • Upgrade

    CVE-2025-68778 lists a fix boundary at a35788ddf8df65837897ecbb0ddb2896b863159e. Compare the installed build with that boundary before you change production.

  • Version check

    Seen in 44f714dae50a2e795d3268a6831762aa6fa54f55 <a35788ddf8df65837897ecbb0ddb2896b863159e

  • Advisory

    Open the cve_org record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-68778. EPSS is 0.20%. Act only if a listed version of Linux Linux is installed.

Which versions are affected?

Compare what you have installed with Linux Linux 44f714dae50a2e795d3268a6831762aa6fa54f55 <a35788ddf8df65837897ecbb0ddb2896b863159e 44f714dae50a2e795d3268a6831762aa6fa54f55 <a35788ddf8df65837897ecbb0ddb2896b863159e. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.20%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jan 13, 2026 · EUVD

    Detected

    In the Linux kernel, the following vulnerability has been resolved: btrfs: don't log conflicting inode if it's a dir moved in the current transaction 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 t

  2. May 11, 2026 · EUVD

    Updated

    In the Linux kernel, the following vulnerability has been resolved: btrfs: don't log conflicting inode if it's a dir moved in the current transaction 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 t

Sources

  • CVE.orgVulnerability recordCVE-2025-68778

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-68778

    30-day exploitation probability 0.20%

    first.org
  • EUVDVulnerability recordEUVD-2026-2322

    In the Linux kernel, the following vulnerability has been resolved: btrfs: don't log conflicting inode if it's a dir moved in the current transaction 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

    euvd.enisa.europa.eu

References

Freshness

Last verified in this catalog Nov 4, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSNov 4, 2026
  • CVE.orgOct 29, 2026
  • EUVDOct 29, 2026