CVE-2025-22127

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-04-16. 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:

f2fs: fix potential deadloop in prepare_compress_overwrite()

Jan Prusakowski reported a kernel hang issue as below:

When running xfstests on linux-next kernel (6.14.0-rc3, 6.12) I encountered a problem in generic/475 test where fsstress process gets blocked in __f2fs_write_data_pages() and the test hangs. The options I used are:

MKFS_OPTIONS -- -O compression -O extra_attr -O project_quota -O quota /dev/vdc MOUNT_OPTIONS -- -o acl,user_xattr -o discard,compress_extension=* /dev/vdc /vdc

INFO: task kworker/u8:0:11 blocked for more than 122 seconds. Not tainted 6.14.0-rc3-xfstests-lockdep #1 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/u8:0 state:D stack:0 pid:11 tgid:11 ppid:2 task_flags:0x4208160 flags:0x00004000 Workqueue: writeback wb_workfn (flush-253:0) Call Trace: __schedule+0x309/0x8e0 schedule+0x3a/0x100 schedule_preempt_disabled+0x15/0x30 __mutex_lock+0x59a/0xdb0 __f2fs_write_data_pages+0x3ac/0x400 do_writepages+0xe8/0x290 __writeback_single_inode+0x5c/0x360 writeback_sb_inodes+0x22f/0x570 wb_writeback+0xb0/0x410 wb_do_writeback+0x47/0x2f0 wb_workfn+0x5a/0x1c0 process_one_work+0x223/0x5b0 worker_thread+0x1d5/0x3c0 kthread+0xfd/0x230 ret_from_fork+0x31/0x50 ret_from_fork_asm+0x1a/0x30

The root cause is: once generic/475 starts toload error table to dm device, f2fs_prepare_compress_overwrite() will loop reading compressed cluster pages due to IO error, meanwhile it has held .writepages lock, it can block all other writeback tasks.

Let's fix this issue w/ below changes:

  • add f2fs_handle_page_eio() in prepare_compress_overwrite() to
detect IO error.
  • detect cp_error earler in f2fs_read_multi_pages().

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
4%
KEV
Not listed

Published

April 16, 2025

Last Modified

September 7, 2026

Advisory Details (3)

Auto-updated Sep 7, 2026
No patch confirmed yet.
generic

f2fs: fix potential deadloop in prepare_compress_overwrite() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7cd460bd9e7c6e6c30a33982603f65fb5deab1e4
generic

f2fs: fix potential deadloop in prepare_compress_overwrite() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7215cf8ef54bdc9082dffac4662416d54961e258
generic

f2fs: fix potential deadloop in prepare_compress_overwrite() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3147ee567dd9004a49826ddeaf0a4b12865d4409

Vendor Advisories for CVE-2025-22127(1)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-22.22) @ plucky2026-09-07ubuntu
ubuntulinux-tools-azure (6.14.0-1007.7) @ plucky2026-09-07ubuntu
ubuntulinux-tools-oracle-64k (6.14.0-1007.7) @ plucky2026-09-07ubuntu
linuxKernel @ 6.14.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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (353 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (176 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.16~rc7-1~exp1 (62 versions)6.16.3-1—

Weakness Classification(1)

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

All Vendor Advisories

(4)

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 5× in last 7d / 29× 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 131 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-22127?
CVE-2025-22127 is a medium vulnerability published on April 16, 2025. In the Linux kernel, the following vulnerability has been resolved: f2fs: fix potential deadloop in preparecompressoverwrite() Jan Prusakowski reported a kernel hang issue as below: When running xfstests on linux-next kernel (6.14.0-rc3, 6.12) I encountered a problem in generic/475 test where…
When was CVE-2025-22127 disclosed?
CVE-2025-22127 was first published in the National Vulnerability Database on April 16, 2025, with the most recent update on September 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-22127 actively exploited?
CVE-2025-22127 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 95.8% of all scored CVEs.
What is the CVSS score of CVE-2025-22127?
CVE-2025-22127 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-22127?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-22127, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2025-22127?

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

Start Free Scan →Browse All CVEs