CVE-2022-49364

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-10-21. 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

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:

f2fs: fix to clear dirty inode in f2fs_evict_inode()

As Yanming reported in bugzilla:

https://bugzilla.kernel.org/show_bug.cgi?id=215904

The kernel message is shown below:

kernel BUG at fs/f2fs/inode.c:825! Call Trace: evict+0x282/0x4e0 __dentry_kill+0x2b2/0x4d0 shrink_dentry_list+0x17c/0x4f0 shrink_dcache_parent+0x143/0x1e0 do_one_tree+0x9/0x30 shrink_dcache_for_umount+0x51/0x120 generic_shutdown_super+0x5c/0x3a0 kill_block_super+0x90/0xd0 kill_f2fs_super+0x225/0x310 deactivate_locked_super+0x78/0xc0 cleanup_mnt+0x2b7/0x480 task_work_run+0xc8/0x150 exit_to_user_mode_prepare+0x14a/0x150 syscall_exit_to_user_mode+0x1d/0x40 do_syscall_64+0x48/0x90

The root cause is: inode node and dnode node share the same nid, so during f2fs_evict_inode(), dnode node truncation will invalidate its NAT entry, so when truncating inode node, it fails due to invalid NAT entry, result in inode is still marked as dirty, fix this issue by clearing dirty for inode and setting SBI_NEED_FSCK flag in filesystem.

output from dump.f2fs: [print_node_info: 354] Node ID [0xf:15] is inode i_nid[0] [0x f : 15]

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

Published

February 26, 2025

Last Modified

October 21, 2025

References (6)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.4.198—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.

Data Freshness Timeline

(refreshed 7× 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.

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

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

Frequently asked(5)

What is CVE-2022-49364?
CVE-2022-49364 is a medium vulnerability published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to clear dirty inode in f2fsevictinode() As Yanming reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=215904 The kernel message is shown below: kernel BUG at fs/f2fs/inode.c:825! Call Trace:…
When was CVE-2022-49364 disclosed?
CVE-2022-49364 was first published in the National Vulnerability Database on February 26, 2025, with the most recent update on October 21, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-49364 actively exploited?
CVE-2022-49364 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 82.7% of all scored CVEs.
What is the CVSS score of CVE-2022-49364?
CVE-2022-49364 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-49364?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-49364, 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-49364

Explore →

Is Your Infrastructure Affected by CVE-2022-49364?

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

Start Free Scan →Browse All CVEs