CVE-2025-38370

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-07-25. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

btrfs: fix failure to rebuild free space tree using multiple transactions

If we are rebuilding a free space tree, while modifying the free space tree we may need to allocate a new metadata block group. If we end up using multiple transactions for the rebuild, when we call btrfs_end_transaction() we enter btrfs_create_pending_block_groups() which calls add_block_group_free_space() to add items to the free space tree for the block group.

Then later during the free space tree rebuild, at btrfs_rebuild_free_space_tree(), we may find such new block groups and call populate_free_space_tree() for them, which fails with -EEXIST because there are already items in the free space tree. Then we abort the transaction with -EEXIST at btrfs_rebuild_free_space_tree(). Notice that we say "may find" the new block groups because a new block group may be inserted in the block groups rbtree, which is being iterated by the rebuild process, before or after the current node where the rebuild process is currently at.

Syzbot recently reported such case which produces a trace like the following:

------------[ cut here ]------------ BTRFS: Transaction aborted (error -17) WARNING: CPU: 1 PID: 7626 at fs/btrfs/free-space-tree.c:1341 btrfs_rebuild_free_space_tree+0x470/0x54c fs/btrfs/free-space-tree.c:1341 Modules linked in: CPU: 1 UID: 0 PID: 7626 Comm: syz.2.25 Not tainted 6.15.0-rc7-syzkaller-00085-gd7fa1af5b33e-dirty #0 PREEMPT Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : btrfs_rebuild_free_space_tree+0x470/0x54c fs/btrfs/free-space-tree.c:1341 lr : btrfs_rebuild_free_space_tree+0x470/0x54c fs/btrfs/free-space-tree.c:1341 sp : ffff80009c4f7740 x29: ffff80009c4f77b0 x28: ffff0000d4c3f400 x27: 0000000000000000 x26: dfff800000000000 x25: ffff70001389eee8 x24: 0000000000000003 x23: 1fffe000182b6e7b x22: 0000000000000000 x21: ffff0000c15b73d8 x20: 00000000ffffffef x19: ffff0000c15b7378 x18: 1fffe0003386f276 x17: ffff80008f31e000 x16: ffff80008adbe98c x15: 0000000000000001 x14: 1fffe0001b281550 x13: 0000000000000000 x12: 0000000000000000 x11: ffff60001b281551 x10: 0000000000000003 x9 : 1c8922000a902c00 x8 : 1c8922000a902c00 x7 : ffff800080485878 x6 : 0000000000000000 x5 : 0000000000000001 x4 : 0000000000000001 x3 : ffff80008047843c x2 : 0000000000000001 x1 : ffff80008b3ebc40 x0 : 0000000000000001 Call trace: btrfs_rebuild_free_space_tree+0x470/0x54c fs/btrfs/free-space-tree.c:1341 (P) btrfs_start_pre_rw_mount+0xa78/0xe10 fs/btrfs/disk-io.c:3074 btrfs_remount_rw fs/btrfs/super.c:1319 [inline] btrfs_reconfigure+0x828/0x2418 fs/btrfs/super.c:1543 reconfigure_super+0x1d4/0x6f0 fs/super.c:1083 do_remount fs/namespace.c:3365 [inline] path_mount+0xb34/0xde0 fs/namespace.c:4200 do_mount fs/namespace.c:4221 [inline] __do_sys_mount fs/namespace.c:4432 [inline] __se_sys_mount fs/namespace.c:4409 [inline] __arm64_sys_mount+0x3e8/0x468 fs/namespace.c:4409 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x58/0x17c arch/arm64/kernel/entry-common.c:767 el0t_64_sync_handler+0x78/0x108 arch/arm64/kernel/entry-common.c:786 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600 irq event stamp: 330 hardirqs last enabled at (329): [] raw_spin_rq_unlock_irq kernel/sched/sched.h:1525 [inline] hardirqs last enabled at (329): [] finish_lock_switch+0xb0/0x1c0 kernel/sched/core.c:5130 hardirqs last disabled at (330): [] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:511 softirqs last enabled at (10): [] local_bh_enable+0 ---truncated---

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

July 25, 2025

Last Modified

November 18, 2025

References (2)

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-edge (6.14.0-1015.15~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-6.14 (6.14.0-1014.14) @ plucky2026-05-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-34.34~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-gcp-edge (6.14.0-1018.19~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.14.0-1014.14~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-aws-edge (6.14.0-1015.15~24.04.1) @ noble2026-05-30ubuntu
linuxKernel @ 6.15.6—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.

All Vendor Advisories

(6)

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 6× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 104 total refreshes for this CVE.

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

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2025-38370?
CVE-2025-38370 is a medium vulnerability published on July 25, 2025. In the Linux kernel, the following vulnerability has been resolved: btrfs: fix failure to rebuild free space tree using multiple transactions If we are rebuilding a free space tree, while modifying the free space tree we may need to allocate a new metadata block group. If we end up using multiple…
When was CVE-2025-38370 disclosed?
CVE-2025-38370 was first published in the National Vulnerability Database on July 25, 2025, with the most recent update on November 18, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-38370 actively exploited?
CVE-2025-38370 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.1% of all scored CVEs.
What is the CVSS score of CVE-2025-38370?
CVE-2025-38370 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-38370?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-38370, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-38370

Explore →

Is Your Infrastructure Affected by CVE-2025-38370?

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

Start Free Scan →Browse All CVEs