CVE-2022-49169

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-10-22. 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: use spin_lock to avoid hang

[14696.634553] task:cat state:D stack: 0 pid:1613738 ppid:1613735 flags:0x00000004 [14696.638285] Call Trace: [14696.639038] [14696.640032] __schedule+0x302/0x930 [14696.640969] schedule+0x58/0xd0 [14696.641799] schedule_preempt_disabled+0x18/0x30 [14696.642890] __mutex_lock.constprop.0+0x2fb/0x4f0 [14696.644035] ? mod_objcg_state+0x10c/0x310 [14696.645040] ? obj_cgroup_charge+0xe1/0x170 [14696.646067] __mutex_lock_slowpath+0x13/0x20 [14696.647126] mutex_lock+0x34/0x40 [14696.648070] stat_show+0x25/0x17c0 [f2fs] [14696.649218] seq_read_iter+0x120/0x4b0 [14696.650289] ? aa_file_perm+0x12a/0x500 [14696.651357] ? lru_cache_add+0x1c/0x20 [14696.652470] seq_read+0xfd/0x140 [14696.653445] full_proxy_read+0x5c/0x80 [14696.654535] vfs_read+0xa0/0x1a0 [14696.655497] ksys_read+0x67/0xe0 [14696.656502] __x64_sys_read+0x1a/0x20 [14696.657580] do_syscall_64+0x3b/0xc0 [14696.658671] entry_SYSCALL_64_after_hwframe+0x44/0xae [14696.660068] RIP: 0033:0x7efe39df1cb2 [14696.661133] RSP: 002b:00007ffc8badd948 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 [14696.662958] RAX: ffffffffffffffda RBX: 0000000000020000 RCX: 00007efe39df1cb2 [14696.664757] RDX: 0000000000020000 RSI: 00007efe399df000 RDI: 0000000000000003 [14696.666542] RBP: 00007efe399df000 R08: 00007efe399de010 R09: 00007efe399de010 [14696.668363] R10: 0000000000000022 R11: 0000000000000246 R12: 0000000000000000 [14696.670155] R13: 0000000000000003 R14: 0000000000020000 R15: 0000000000020000 [14696.671965] [14696.672826] task:umount state:D stack: 0 pid:1614985 ppid:1614984 flags:0x00004000 [14696.674930] Call Trace: [14696.675903] [14696.676780] __schedule+0x302/0x930 [14696.677927] schedule+0x58/0xd0 [14696.679019] schedule_preempt_disabled+0x18/0x30 [14696.680412] __mutex_lock.constprop.0+0x2fb/0x4f0 [14696.681783] ? destroy_inode+0x65/0x80 [14696.683006] __mutex_lock_slowpath+0x13/0x20 [14696.684305] mutex_lock+0x34/0x40 [14696.685442] f2fs_destroy_stats+0x1e/0x60 [f2fs] [14696.686803] f2fs_put_super+0x158/0x390 [f2fs] [14696.688238] generic_shutdown_super+0x7a/0x120 [14696.689621] kill_block_super+0x27/0x50 [14696.690894] kill_f2fs_super+0x7f/0x100 [f2fs] [14696.692311] deactivate_locked_super+0x35/0xa0 [14696.693698] deactivate_super+0x40/0x50 [14696.694985] cleanup_mnt+0x139/0x190 [14696.696209] __cleanup_mnt+0x12/0x20 [14696.697390] task_work_run+0x64/0xa0 [14696.698587] exit_to_user_mode_prepare+0x1b7/0x1c0 [14696.700053] syscall_exit_to_user_mode+0x27/0x50 [14696.701418] do_syscall_64+0x48/0xc0 [14696.702630] entry_SYSCALL_64_after_hwframe+0x44/0xae

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 13, 2026

Advisory Details (4)

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

f2fs: use spin_lock to avoid hang - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/98237fcda4a24e67b0a4498c17d5aa4ad4537bc7
generic

f2fs: use spin_lock to avoid hang - kernel/git/stable/linux.git - Linux kernel stable tree

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

f2fs: use spin_lock to avoid hang - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/738886004bd2885ac2db0bc63b4874aa471ca87e
generic

f2fs: use spin_lock to avoid hang - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2eff60346e7ae1a24cd868b8fdcf58e946e7dde1

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.15.33—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
linux—5.17.3-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—5.17.3-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—5.17.3-1—

Data Freshness Timeline

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

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

Related CVEs(same product)

Frequently asked(5)

What is CVE-2022-49169?
CVE-2022-49169 is a medium vulnerability published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: f2fs: use spin_lock to avoid hang [14696.634553] task:cat state:D stack: 0 pid:1613738 ppid:1613735 flags:0x00000004 [14696.638285] Call Trace: [14696.639038] <TASK> [14696.640032] schedule+0x302/0x930 [14696.640969]…
When was CVE-2022-49169 disclosed?
CVE-2022-49169 was first published in the National Vulnerability Database on February 26, 2025, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-49169 actively exploited?
CVE-2022-49169 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.8% of all scored CVEs.
What is the CVSS score of CVE-2022-49169?
CVE-2022-49169 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-49169?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-49169, 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-49169

Explore →

Is Your Infrastructure Affected by CVE-2022-49169?

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

Start Free Scan →Browse All CVEs