CVE-2022-49380

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 avoid f2fs_bug_on() in dec_valid_node_count()

As Yanming reported in bugzilla:

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

I have encountered a bug in F2FS file system in kernel v5.17.

The kernel should enable CONFIG_KASAN=y and CONFIG_KASAN_INLINE=y. You can reproduce the bug by running the following commands:

The kernel message is shown below:

kernel BUG at fs/f2fs/f2fs.h:2511! Call Trace: f2fs_remove_inode_page+0x2a2/0x830 f2fs_evict_inode+0x9b7/0x1510 evict+0x282/0x4e0 do_unlinkat+0x33a/0x540 __x64_sys_unlinkat+0x8e/0xd0 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae

The root cause is: .total_valid_block_count or .total_valid_node_count could fuzzed to zero, then once dec_valid_node_count() was called, it will cause BUG_ON(), this patch fixes to print warning info and set SBI_NEED_FSCK into CP instead of panic.

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

Published

February 26, 2025

Last Modified

August 15, 2026

Advisory Details (6)

Auto-updated Aug 15, 2026
No patch confirmed yet.
generic

f2fs: fix to avoid f2fs_bug_on() in dec_valid_node_count() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4d17e6fe9293d57081ffdc11e1cf313e25e8fd9e
generic

f2fs: fix to avoid f2fs_bug_on() in dec_valid_node_count() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ccffa99ae6a1f44797b57444c6a80382a42928fe
generic

f2fs: fix to avoid f2fs_bug_on() in dec_valid_node_count() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/89d9a48d0cd30429463ea4e37ca83be6773ed5eb
generic

f2fs: fix to avoid f2fs_bug_on() in dec_valid_node_count() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bce859358d3d5940aa858e40ceee70ee6e76130e
generic

f2fs: fix to avoid f2fs_bug_on() in dec_valid_node_count() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2766ddaf45b69252bb8fe526b5b6e56904a9ae7a
generic

f2fs: fix to avoid f2fs_bug_on() in dec_valid_node_count() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f8b3c3fcf33105bc1ee7788e3b51b0a1ae42ae53

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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (14 versions)5.10.127-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—5.18.5-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—5.18.5-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—5.18.5-1—

Data Freshness Timeline

(refreshed 4× in last 7d / 22× 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 153 total refreshes for this CVE.

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

Related CVEs(same product)

Frequently asked(5)

What is CVE-2022-49380?
CVE-2022-49380 is a medium vulnerability published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid f2fsbugon() in decvalidnode_count() As Yanming reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=215897 I have encountered a bug in F2FS file system in kernel v5.17. The kernel should enable…
When was CVE-2022-49380 disclosed?
CVE-2022-49380 was first published in the National Vulnerability Database on February 26, 2025, with the most recent update on August 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-49380 actively exploited?
CVE-2022-49380 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 81.7% of all scored CVEs.
What is the CVSS score of CVE-2022-49380?
CVE-2022-49380 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-49380?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-49380, 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-2022-49380

Explore →

Is Your Infrastructure Affected by CVE-2022-49380?

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

Start Free Scan →Browse All CVEs