CVE-2025-68778

UNRATEDCVSS · not yet scored

Also known asEUVD-2026-2322 (ENISA EUVD) · GHSA-g468-fxhj-fm89 (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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" has inode A as its parent directory;

2) We move "dir1" to some other directory;

3) We create a file with the name "dir1" in directory inode A;

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";

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();

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);

7) We have a power failure;

8) Next time the fs is mounted, log replay happens and when processing the inode for directory "dir1" we find a new INODE_REF and add that link, but we don't remove the old link of the inode since we have not logged the old parent directory of the directory inode "dir1".

As a result after log replay finishes when we trigger writeback of the subvolume tree's extent buffers, the tree check will detect that we have a directory a hard link count of 2 and we get a mount failure. The errors and stack traces reported in dmesg/syslog are like this:

[ 3845.729764] BTRFS info (device dm-0): start tree-log replay [ 3845.730304] page: refcount:3 mapcount:0 mapping:000000005c8a3027 index:0x1d00 pfn:0x11510c [ 3845.731236] memcg:ffff9264c02f4e00 [ 3845.731751] aops:btree_aops [btrfs] ino:1 [ 3845.732300] flags: 0x17fffc00000400a(uptodate|private|writeback|node=0|zone=2|lastcpupid=0x1ffff) [ 3845.733346] raw: 017fffc00000400a 0000000000000000 dead000000000122 ffff9264d978aea8 [ 3845.734265] raw: 0000000000001d00 ffff92650e6d4738 00000003ffffffff ffff9264c02f4e00 [ 3845.735305] page dumped because: eb page dump [ 3845.735981] BTRFS critical (device dm-0): corrupt leaf: root=5 block=30408704 slot=6 ino=257, invalid nlink: has 2 expect no more than 1 for dir [ 3845.737786] BTRFS info (device dm-0): leaf 30408704 gen 10 total ptrs 17 free space 14881 owner 5 [ 3845.737789] BTRFS info (device dm-0): refs 4 lock_owner 0 current 30701 [ 3845.737792] item 0 key (256 INODE_ITEM 0) itemoff 16123 itemsize 160 [ 3845.737794] inode generation 3 transid 9 size 16 nbytes 16384 [ 3845.737795] block group 0 mode 40755 links 1 uid 0 gid 0 [ 3845.737797] rdev 0 sequence 2 flags 0x0 [ 3845.737798] atime 1764259517.0 [ 3845.737800] ctime 1764259517.572889464 [ 3845.737801] mtime 1764259517.572889464 [ 3845.737802] otime 1764259517.0 [ 3845.737803] item 1 key (256 INODE_REF 256) itemoff 16111 itemsize 12 [ 3845.737805] index 0 name_len 2 [ 3845.737807] item 2 key (256 DIR_ITEM 2363071922) itemoff 16077 itemsize 34 [ 3845.737808] location key (257 1 0) type 2 [ 3845.737810] transid 9 data_len 0 name_len 4 [ 3845.737811] item 3 key (256 DIR_ITEM 2676584006) itemoff 16043 itemsize 34 [ 3845.737813] location key (258 1 0) type 2 [ 3845.737814] transid 9 data_len 0 name_len 4 [ 3845.737815] item 4 key (256 DIR_INDEX 2) itemoff 16009 itemsize 34 [ 3845.737816] location key (257 1 0) type 2 [ ---truncated---

CVSS
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
9th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

January 13, 2026

Last Modified

June 17, 2026

Vendor Advisories for CVE-2025-68778(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(21)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-nvidia-64k-6.8 (6.8.0-1051.54) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2042.43) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1011.11) @ questing2026-10-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1051.54.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1049.50) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1054.57~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi-6.17 (6.17.0-1014.14) @ questing2026-10-27ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1054.60) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1022.22) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1054.60+fips1) @ noble2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-22.22) @ questing2026-10-27ubuntu
ubuntulinux-virtual-6.8 (6.8.0-110.110) @ noble2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1010.11~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-64k-6.17 (6.17.0-1012.12) @ questing2026-10-27ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1059.65~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-110.110~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1047.48) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1054.57+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1013.13) @ questing2026-10-27ubuntu
linuxKernel @ 6.1.160 (fixes >=4.8.0)—osv

These rows come from Ubuntu and OSV. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
linux-6.16.1.106-3~deb11u1 ... 6.1.159-1~deb11u1 (14 versions)
  • every version up to 6.1.162-1~deb11u1: fixed in 6.1.162-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (46 versions)
  • every version up to 6.1.162-1: fixed in 6.1.162-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.69-1~bpo12+1 (10 versions)
  • every version up to 6.12.69-1: fixed in 6.12.69-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (93 versions)
  • every version up to 6.18.3-1: fixed in 6.18.3-1
—

Additional Vendor Advisories

(20)

Data Freshness Timeline

(refreshed 6× in last 7d / 32× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 250 rows on record for this CVE, as 99 entries (1 repeat merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 150 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-21 16:37 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-11-19 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  4. 2026-11-18 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  5. 2026-11-17 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  6. 2026-11-16 16:47 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-11-15 16:52 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-11-14 16:38 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  13. 2026-11-09 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-11-08 16:37 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-11-07 16:37 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  17. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-11-03 16:45 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  22. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  23. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  24. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  25. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
Show 74 more
  1. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-10-27 10:54 UTCEchelonGraph re-scored
  3. 2026-10-27 10:54 UTCVendor advisory
  4. 2026-10-27 10:53 UTCGHSA enrichmentGHSA-g468-fxhj-fm89
  5. 2026-10-27 04:55 UTCOSV refresh
  6. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  7. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  8. 2026-10-25 16:04 UTCEchelonGraph re-scored
  9. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  10. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  11. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  12. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  13. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  14. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  15. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-10-18 05:17 UTCEchelonGraph re-scored
  17. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  18. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-10-12 16:47 UTCEchelonGraph re-scored
  22. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-10-11 20:21 UTCEchelonGraph re-scored
  24. 2026-10-11 18:33 UTCEchelonGraph re-scored
  25. 2026-10-11 15:08 UTCEchelonGraph re-scored
  26. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  27. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  28. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  29. 2026-10-08 21:58 UTCOSV refresh
  30. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  31. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  32. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  33. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  34. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  35. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  36. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  37. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  38. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  39. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  40. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  41. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  42. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  43. 2026-09-19 04:36 UTCOSV refresh
  44. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  45. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  46. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  47. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  48. 2026-09-15 03:10 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  49. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  50. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  51. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  52. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  53. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  54. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  55. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  56. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  57. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  58. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  59. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  60. 2026-08-31 08:25 UTCOSV refresh
  61. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  62. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  63. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  64. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  65. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  66. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  67. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  68. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  69. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  70. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  71. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  72. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  73. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  74. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.2% · 7th percentile

Frequently asked(4)

What is CVE-2025-68778?
CVE-2025-68778 is a vulnerability whose severity is not yet rated; its CVE record was published on January 13, 2026. 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…
When was the CVE record for CVE-2025-68778 published?
The CVE record for CVE-2025-68778 was published on January 13, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2025-68778 actively exploited?
CVE-2025-68778 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
How do I remediate CVE-2025-68778?
A fix for CVE-2025-68778 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-68778 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-68778

Explore →

Is Your Infrastructure Affected by CVE-2025-68778?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.