CVE-2025-71194

UNRATEDCVSS · not yet scored

Also known asEUVD-2025-206804 (ENISA EUVD) · GHSA-g466-9rmr-2m23 (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: fix deadlock in wait_current_trans() due to ignored transaction type

When wait_current_trans() is called during start_transaction(), it currently waits for a blocked transaction without considering whether the given transaction type actually needs to wait for that particular transaction state. The btrfs_blocked_trans_types[] array already defines which transaction types should wait for which transaction states, but this check was missing in wait_current_trans().

This can lead to a deadlock scenario involving two transactions and pending ordered extents:

  • Transaction A is in TRANS_STATE_COMMIT_DOING state
  • A worker processing an ordered extent calls start_transaction()
with TRANS_JOIN
  • join_transaction() returns -EBUSY because Transaction A is in
TRANS_STATE_COMMIT_DOING
  • Transaction A moves to TRANS_STATE_UNBLOCKED and completes
  • A new Transaction B is created (TRANS_STATE_RUNNING)
  • The ordered extent from step 2 is added to Transaction B's
pending ordered extents
  • Transaction B immediately starts commit by another task and
enters TRANS_STATE_COMMIT_START
  • The worker finally reaches wait_current_trans(), sees Transaction B
in TRANS_STATE_COMMIT_START (a blocked state), and waits unconditionally
  • However, TRANS_JOIN should NOT wait for TRANS_STATE_COMMIT_START
according to btrfs_blocked_trans_types[]
  • Transaction B is waiting for pending ordered extents to complete
  • Deadlock: Transaction B waits for ordered extent, ordered extent
waits for Transaction B

This can be illustrated by the following call stacks: CPU0 CPU1 btrfs_finish_ordered_io() start_transaction(TRANS_JOIN) join_transaction() # -EBUSY (Transaction A is # TRANS_STATE_COMMIT_DOING) # Transaction A completes # Transaction B created # ordered extent added to # Transaction B's pending list btrfs_commit_transaction() # Transaction B enters # TRANS_STATE_COMMIT_START # waiting for pending ordered # extents wait_current_trans() # waits for Transaction B # (should not wait!)

Task bstore_kv_sync in btrfs_commit_transaction waiting for ordered extents:

__schedule+0x2e7/0x8a0 schedule+0x64/0xe0 btrfs_commit_transaction+0xbf7/0xda0 [btrfs] btrfs_sync_file+0x342/0x4d0 [btrfs] __x64_sys_fdatasync+0x4b/0x80 do_syscall_64+0x33/0x40 entry_SYSCALL_64_after_hwframe+0x44/0xa9

Task kworker in wait_current_trans waiting for transaction commit:

Workqueue: btrfs-syno_nocow btrfs_work_helper [btrfs] __schedule+0x2e7/0x8a0 schedule+0x64/0xe0 wait_current_trans+0xb0/0x110 [btrfs] start_transaction+0x346/0x5b0 [btrfs] btrfs_finish_ordered_io.isra.0+0x49b/0x9c0 [btrfs] btrfs_work_helper+0xe8/0x350 [btrfs] process_one_work+0x1d3/0x3c0 worker_thread+0x4d/0x3e0 kthread+0x12d/0x150 ret_from_fork+0x1f/0x30

Fix this by passing the transaction type to wait_current_trans() and checking btrfs_blocked_trans_types[cur_trans->state] against the given type before deciding to wait. This ensures that transaction types which are allowed to join during certain blocked states will not unnecessarily wait and cause deadlocks.

CVSS v3
—
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
6th
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: 60 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)60 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 Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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

February 4, 2026

Last Modified

October 19, 2026

References (7)

Vendor Advisories for CVE-2025-71194(1)

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

Patch Availability(29)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1110.95) @ jammy2026-10-19ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.176.161) @ jammy2026-10-19ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1057.57~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1057.57) @ jammy2026-10-19ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.176.186~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1105.95) @ jammy2026-10-19ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1104.108) @ jammy2026-10-19ubuntu
ubuntulinux-tools-ibm-5.15 (5.15.0.1099.95) @ jammy2026-10-19ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-tools-kvm-5.15 (5.15.0.1097.93) @ jammy2026-10-19ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1099.97) @ jammy2026-10-19ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1070 (5.15.0-1070.74) @ jammy2026-10-19ubuntu
ubuntulinux-virtual-6.8 (6.8.0-117.117) @ noble2026-10-19ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1054.57.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1106.115~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-116.116+fips1) @ noble2026-10-19ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1024.24) @ noble2026-10-19ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1054.57~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1056.62) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1059.65+fips1) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1059.65~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-10-19ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.17.0-1018.20~24.04.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1030.30) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1021.21~24.04.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-fde-6.17 (6.17.0-1018.18~24.04.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1019.19~24.04.3+1) @ noble2026-10-19ubuntu
ubuntulinux-tools-nvidia-hwe-24.04 (6.17.0-1031.31) @ noble2026-10-19ubuntu
linuxKernel @ 5.10.249 (fixes >=3.11.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). 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 ... 5.10.92-2 (48 versions)
  • every version up to 5.10.249-1: fixed in 5.10.249-1
—
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 (96 versions)
  • every version up to 6.18.8-1: fixed in 6.18.8-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 39× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

Showing the most recent 99 of 228 refreshes on record for this CVE.

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 129 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(4)

What is CVE-2025-71194?
CVE-2025-71194 is a vulnerability whose severity is not yet rated; its CVE record was published on February 4, 2026. In the Linux kernel, the following vulnerability has been resolved: btrfs: fix deadlock in wait_current_trans() due to ignored transaction type When wait_current_trans() is called during start_transaction(), it currently waits for a blocked transaction without considering whether the given…
When was the CVE record for CVE-2025-71194 published?
The CVE record for CVE-2025-71194 was published on February 4, 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 October 19, 2026; the record at its source may have been updated since.
Is CVE-2025-71194 actively exploited?
CVE-2025-71194 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
How do I remediate CVE-2025-71194?
A fix for CVE-2025-71194 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-71194 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-71194

Explore →

Is Your Infrastructure Affected by CVE-2025-71194?

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

Book a Demo →Browse All CVEs