CVE-2025-21942

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-04-01. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2025-9379 (ENISA EUVD) · GHSA-f349-gqv8-wh65 (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 fixed version is listed under Patch Availability — apply it.

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

btrfs: zoned: fix extent range end unlock in cow_file_range()

Running generic/751 on the for-next branch often results in a hang like below. They are both stack by locking an extent. This suggests someone forget to unlock an extent.

INFO: task kworker/u128:1:12 blocked for more than 323 seconds. Not tainted 6.13.0-BTRFS-ZNS+ #503 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/u128:1 state:D stack:0 pid:12 tgid:12 ppid:2 flags:0x00004000 Workqueue: btrfs-fixup btrfs_work_helper [btrfs] Call Trace: __schedule+0x534/0xdd0 schedule+0x39/0x140 __lock_extent+0x31b/0x380 [btrfs] ? __pfx_autoremove_wake_function+0x10/0x10 btrfs_writepage_fixup_worker+0xf1/0x3a0 [btrfs] btrfs_work_helper+0xff/0x480 [btrfs] ? lock_release+0x178/0x2c0 process_one_work+0x1ee/0x570 ? srso_return_thunk+0x5/0x5f worker_thread+0x1d1/0x3b0 ? __pfx_worker_thread+0x10/0x10 kthread+0x10b/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x30/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 INFO: task kworker/u134:0:184 blocked for more than 323 seconds. Not tainted 6.13.0-BTRFS-ZNS+ #503 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/u134:0 state:D stack:0 pid:184 tgid:184 ppid:2 flags:0x00004000 Workqueue: writeback wb_workfn (flush-btrfs-4) Call Trace: __schedule+0x534/0xdd0 schedule+0x39/0x140 __lock_extent+0x31b/0x380 [btrfs] ? __pfx_autoremove_wake_function+0x10/0x10 find_lock_delalloc_range+0xdb/0x260 [btrfs] writepage_delalloc+0x12f/0x500 [btrfs] ? srso_return_thunk+0x5/0x5f extent_write_cache_pages+0x232/0x840 [btrfs] btrfs_writepages+0x72/0x130 [btrfs] do_writepages+0xe7/0x260 ? srso_return_thunk+0x5/0x5f ? lock_acquire+0xd2/0x300 ? srso_return_thunk+0x5/0x5f ? find_held_lock+0x2b/0x80 ? wbc_attach_and_unlock_inode.part.0+0x102/0x250 ? wbc_attach_and_unlock_inode.part.0+0x102/0x250 __writeback_single_inode+0x5c/0x4b0 writeback_sb_inodes+0x22d/0x550 __writeback_inodes_wb+0x4c/0xe0 wb_writeback+0x2f6/0x3f0 wb_workfn+0x32a/0x510 process_one_work+0x1ee/0x570 ? srso_return_thunk+0x5/0x5f worker_thread+0x1d1/0x3b0 ? __pfx_worker_thread+0x10/0x10 kthread+0x10b/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x30/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30

This happens because we have another success path for the zoned mode. When there is no active zone available, btrfs_reserve_extent() returns -EAGAIN. In this case, we have two reactions.

(1) If the given range is never allocated, we can only wait for someone to finish a zone, so wait on BTRFS_FS_NEED_ZONE_FINISH bit and retry afterward.

(2) Or, if some allocations are already done, we must bail out and let the caller to send IOs for the allocation. This is because these IOs may be necessary to finish a zone.

The commit 06f364284794 ("btrfs: do proper folio cleanup when cow_file_range() failed") moved the unlock code from the inside of the loop to the outside. So, previously, the allocated extents are unlocked just after the allocation and so before returning from the function. However, they are no longer unlocked on the case (2) above. That caused the hang issue.

Fix the issue by modifying the 'end' to the end of the allocated range. Then, we can exit the loop and the same unlock code can properly handle the case.

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 fixed version is listed under Patch Availability. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
15th
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-29). 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 fixed version is listed under Patch Availability. 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

April 1, 2025

Last Modified

October 30, 2026

Advisory Details (3)

Auto-updated Oct 30, 2026
Fixed version listed under Patch Availability.
Web page

btrfs: zoned: fix extent range end unlock in cow_file_range() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5a4041f2c47247575a6c2e53ce14f7b0ac946c33
Web page

btrfs: zoned: fix extent range end unlock in cow_file_range() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3fcff2f55389306482ab049b4321bda49495e546
Web page

btrfs: zoned: fix extent range end unlock in cow_file_range() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5f4863cfb29a7b4fe7625ce148d0b9000b75b802

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 6.13.7 (fixes >=6.13.2)—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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 42× 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 197 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 101 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-21942?
CVE-2025-21942 is a medium-severity vulnerability; its CVE record was published on April 1, 2025. In the Linux kernel, the following vulnerability has been resolved: btrfs: zoned: fix extent range end unlock in cow_file_range() Running generic/751 on the for-next branch often results in a hang like below. They are both stack by locking an extent. This suggests someone forget to unlock an…
When was the CVE record for CVE-2025-21942 published?
The CVE record for CVE-2025-21942 was published on April 1, 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 30, 2026; the record at its source may have been updated since.
Is CVE-2025-21942 actively exploited?
CVE-2025-21942 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-21942?
CVE-2025-21942 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-21942?
A fixed version for CVE-2025-21942 is listed under Patch Availability on this page: update to the version listed for your package.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-21942?

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

Book a Demo →Browse All CVEs