CVE-2022-49414

MEDIUMNVD 4.74.7—
EchelonGraph scoreMEDIUM confidence

Score 4.7 from GitHub Security Advisory published 2025-04-17. NVD baseline CVSS 4.7; sources differ by 0.0.

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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

ext4: fix race condition between ext4_write and ext4_convert_inline_data

Hulk Robot reported a BUG_ON: ================================================================== EXT4-fs error (device loop3): ext4_mb_generate_buddy:805: group 0, block bitmap and bg descriptor inconsistent: 25 vs 31513 free clusters kernel BUG at fs/ext4/ext4_jbd2.c:53! invalid opcode: 0000 [#1] SMP KASAN PTI CPU: 0 PID: 25371 Comm: syz-executor.3 Not tainted 5.10.0+ #1 RIP: 0010:ext4_put_nojournal fs/ext4/ext4_jbd2.c:53 [inline] RIP: 0010:__ext4_journal_stop+0x10e/0x110 fs/ext4/ext4_jbd2.c:116 [...] Call Trace: ext4_write_inline_data_end+0x59a/0x730 fs/ext4/inline.c:795 generic_perform_write+0x279/0x3c0 mm/filemap.c:3344 ext4_buffered_write_iter+0x2e3/0x3d0 fs/ext4/file.c:270 ext4_file_write_iter+0x30a/0x11c0 fs/ext4/file.c:520 do_iter_readv_writev+0x339/0x3c0 fs/read_write.c:732 do_iter_write+0x107/0x430 fs/read_write.c:861 vfs_writev fs/read_write.c:934 [inline] do_pwritev+0x1e5/0x380 fs/read_write.c:1031 [...] ==================================================================

Above issue may happen as follows: cpu1 cpu2 __________________________|__________________________ do_pwritev vfs_writev do_iter_write ext4_file_write_iter ext4_buffered_write_iter generic_perform_write ext4_da_write_begin vfs_fallocate ext4_fallocate ext4_convert_inline_data ext4_convert_inline_data_nolock ext4_destroy_inline_data_nolock clear EXT4_STATE_MAY_INLINE_DATA ext4_map_blocks ext4_ext_map_blocks ext4_mb_new_blocks ext4_mb_regular_allocator ext4_mb_good_group_nolock ext4_mb_init_group ext4_mb_init_cache ext4_mb_generate_buddy --> error ext4_test_inode_state(inode, EXT4_STATE_MAY_INLINE_DATA) ext4_restore_inline_data set EXT4_STATE_MAY_INLINE_DATA ext4_block_write_begin ext4_da_write_end ext4_test_inode_state(inode, EXT4_STATE_MAY_INLINE_DATA) ext4_write_inline_data_end handle=NULL ext4_journal_stop(handle) __ext4_journal_stop ext4_put_nojournal(handle) ref_cnt = (unsigned long)handle BUG_ON(ref_cnt == 0) ---> BUG_ON

The lock held by ext4_convert_inline_data is xattr_sem, but the lock held by generic_perform_write is i_rwsem. Therefore, the two locks can be concurrent.

To solve above issue, we add inode_lock() for ext4_convert_inline_data(). At the same time, move ext4_convert_inline_data() in front of ext4_punch_hole(), remove similar handling from ext4_punch_hole().

CVSS v3
4.7
EG Score
4.7(medium)
EG Risk
21(Track)
EG Risk 21/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
Severity47% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

February 26, 2025

Last Modified

October 1, 2025

References (6)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.4.207—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 12× in last 7d / 45× 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.

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

Frequently asked(5)

What is CVE-2022-49414?
CVE-2022-49414 is a medium vulnerability published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: ext4: fix race condition between ext4write and ext4convertinlinedata Hulk Robot reported a BUG_ON: ================================================================== EXT4-fs error (device loop3): ext4mbgenerate_buddy:805: group 0,…
When was CVE-2022-49414 disclosed?
CVE-2022-49414 was first published in the National Vulnerability Database on February 26, 2025, with the most recent update on October 1, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-49414 actively exploited?
CVE-2022-49414 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 91.2% of all scored CVEs.
What is the CVSS score of CVE-2022-49414?
CVE-2022-49414 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2022-49414?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-49414, 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-2022-49414

Explore →

Is Your Infrastructure Affected by CVE-2022-49414?

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

Start Free Scan →Browse All CVEs