CVE-2025-21754

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-5154 (ENISA EUVD) · GHSA-rv8h-hrgv-p5cw (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

btrfs: fix assertion failure when splitting ordered extent after transaction abort

If while we are doing a direct IO write a transaction abort happens, we mark all existing ordered extents with the BTRFS_ORDERED_IOERR flag (done at btrfs_destroy_ordered_extents()), and then after that if we enter btrfs_split_ordered_extent() and the ordered extent has bytes left (meaning we have a bio that doesn't cover the whole ordered extent, see details at btrfs_extract_ordered_extent()), we will fail on the following assertion at btrfs_split_ordered_extent():

ASSERT(!(flags & ~BTRFS_ORDERED_TYPE_FLAGS));

because the BTRFS_ORDERED_IOERR flag is set and the definition of BTRFS_ORDERED_TYPE_FLAGS is just the union of all flags that identify the type of write (regular, nocow, prealloc, compressed, direct IO, encoded).

Fix this by returning an error from btrfs_extract_ordered_extent() if we find the BTRFS_ORDERED_IOERR flag in the ordered extent. The error will be the error that resulted in the transaction abort or -EIO if no transaction abort happened.

This was recently reported by syzbot with the following trace:

FAULT_INJECTION: forcing a failure. name failslab, interval 1, probability 0, space 0, times 1 CPU: 0 UID: 0 PID: 5321 Comm: syz.0.0 Not tainted 6.13.0-rc5-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 fail_dump lib/fault-inject.c:53 [inline] should_fail_ex+0x3b0/0x4e0 lib/fault-inject.c:154 should_failslab+0xac/0x100 mm/failslab.c:46 slab_pre_alloc_hook mm/slub.c:4072 [inline] slab_alloc_node mm/slub.c:4148 [inline] __do_kmalloc_node mm/slub.c:4297 [inline] __kmalloc_noprof+0xdd/0x4c0 mm/slub.c:4310 kmalloc_noprof include/linux/slab.h:905 [inline] kzalloc_noprof include/linux/slab.h:1037 [inline] btrfs_chunk_alloc_add_chunk_item+0x244/0x1100 fs/btrfs/volumes.c:5742 reserve_chunk_space+0x1ca/0x2c0 fs/btrfs/block-group.c:4292 check_system_chunk fs/btrfs/block-group.c:4319 [inline] do_chunk_alloc fs/btrfs/block-group.c:3891 [inline] btrfs_chunk_alloc+0x77b/0xf80 fs/btrfs/block-group.c:4187 find_free_extent_update_loop fs/btrfs/extent-tree.c:4166 [inline] find_free_extent+0x42d1/0x5810 fs/btrfs/extent-tree.c:4579 btrfs_reserve_extent+0x422/0x810 fs/btrfs/extent-tree.c:4672 btrfs_new_extent_direct fs/btrfs/direct-io.c:186 [inline] btrfs_get_blocks_direct_write+0x706/0xfa0 fs/btrfs/direct-io.c:321 btrfs_dio_iomap_begin+0xbb7/0x1180 fs/btrfs/direct-io.c:525 iomap_iter+0x697/0xf60 fs/iomap/iter.c:90 __iomap_dio_rw+0xeb9/0x25b0 fs/iomap/direct-io.c:702 btrfs_dio_write fs/btrfs/direct-io.c:775 [inline] btrfs_direct_write+0x610/0xa30 fs/btrfs/direct-io.c:880 btrfs_do_write_iter+0x2a0/0x760 fs/btrfs/file.c:1397 do_iter_readv_writev+0x600/0x880 vfs_writev+0x376/0xba0 fs/read_write.c:1050 do_pwritev fs/read_write.c:1146 [inline] __do_sys_pwritev2 fs/read_write.c:1204 [inline] __se_sys_pwritev2+0x196/0x2b0 fs/read_write.c:1195 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f1281f85d29 RSP: 002b:00007f12819fe038 EFLAGS: 00000246 ORIG_RAX: 0000000000000148 RAX: ffffffffffffffda RBX: 00007f1282176080 RCX: 00007f1281f85d29 RDX: 0000000000000001 RSI: 0000000020000240 RDI: 0000000000000005 RBP: 00007f12819fe090 R08: 0000000000000000 R09: 0000000000000003 R10: 0000000000007000 R11: 0000000000000246 R12: 0000000000000002 R13: 0000000000000000 R14: 00007f1282176080 R15: 00007ffcb9e23328 BTRFS error (device loop0 state A): Transaction aborted (error -12) BTRFS: error (device loop0 state A ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
14th
KEV
Not listed

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

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). 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
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA 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 SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

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

February 27, 2025

Last Modified

October 28, 2025

References (4)

Patch Availability(13)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oracle-64k (6.11.0-1016.17) @ oracular2026-10-24ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-64.67~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-virtual-6.8 (6.8.0-64.67) @ noble2026-10-24ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1025.26) @ noble2026-10-24ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-64.67.1) @ noble2026-10-24ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1029.30) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure-nvidia-lts-24.04 (6.8.0-1022.23) @ noble2026-10-24ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-26.26) @ oracular2026-10-24ubuntu
ubuntulinux-tools-aws (6.11.0-1014.15) @ oracular2026-10-24ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2026.27) @ noble2026-10-24ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1031.35) @ noble2026-10-24ubuntu
ubuntulinux-tools-gcp-lts-24.04 (6.8.0-1033.35) @ noble2026-10-24ubuntu
linuxKernel @ 6.6.78 (fixes >=6.5.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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.15-1: fixed in 6.12.15-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.15-1: fixed in 6.12.15-1
—

Weakness Classification(1)

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

All Vendor Advisories

(12)

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 96 of 193 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 97 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-21754?
CVE-2025-21754 is a medium-severity vulnerability; its CVE record was published on February 27, 2025. In the Linux kernel, the following vulnerability has been resolved: btrfs: fix assertion failure when splitting ordered extent after transaction abort If while we are doing a direct IO write a transaction abort happens, we mark all existing ordered extents with the BTRFS_ORDERED_IOERR flag (done at…
When was the CVE record for CVE-2025-21754 published?
The CVE record for CVE-2025-21754 was published on February 27, 2025. 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 28, 2025; the record at its source may have been updated since.
Is CVE-2025-21754 actively exploited?
CVE-2025-21754 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-21754?
CVE-2025-21754 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-21754?
A fix for CVE-2025-21754 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-21754?

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

Book a Demo →Browse All CVEs