CVE-2022-50270

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2025-09-15. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: 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 the assign logic of iocb

commit 18ae8d12991b ("f2fs: show more DIO information in tracepoint") introduces iocb field in 'f2fs_direct_IO_enter' trace event And it only assigns the pointer and later it accesses its field in trace print log.

Unable to handle kernel paging request at virtual address ffffffc04cef3d30 Mem abort info: ESR = 0x96000007 EC = 0x25: DABT (current EL), IL = 32 bits

pc : trace_raw_output_f2fs_direct_IO_enter+0x54/0xa4 lr : trace_raw_output_f2fs_direct_IO_enter+0x2c/0xa4 sp : ffffffc0443cbbd0 x29: ffffffc0443cbbf0 x28: ffffff8935b120d0 x27: ffffff8935b12108 x26: ffffff8935b120f0 x25: ffffff8935b12100 x24: ffffff8935b110c0 x23: ffffff8935b10000 x22: ffffff88859a936c x21: ffffff88859a936c x20: ffffff8935b110c0 x19: ffffff8935b10000 x18: ffffffc03b195060 x17: ffffff8935b11e76 x16: 00000000000000cc x15: ffffffef855c4f2c x14: 0000000000000001 x13: 000000000000004e x12: ffff0000ffffff00 x11: ffffffef86c350d0 x10: 00000000000010c0 x9 : 000000000fe0002c x8 : ffffffc04cef3d28 x7 : 7f7f7f7f7f7f7f7f x6 : 0000000002000000 x5 : ffffff8935b11e9a x4 : 0000000000006250 x3 : ffff0a00ffffff04 x2 : 0000000000000002 x1 : ffffffef86a0a31f x0 : ffffff8935b10000 Call trace: trace_raw_output_f2fs_direct_IO_enter+0x54/0xa4 print_trace_fmt+0x9c/0x138 print_trace_line+0x154/0x254 tracing_read_pipe+0x21c/0x380 vfs_read+0x108/0x3ac ksys_read+0x7c/0xec __arm64_sys_read+0x20/0x30 invoke_syscall+0x60/0x150 el0_svc_common.llvm.1237943816091755067+0xb8/0xf8 do_el0_svc+0x28/0xa0

Fix it by copying the required variables for printing and while at it fix the similar issue at some other places in the same file.

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

Published

September 15, 2025

Last Modified

August 5, 2026

References (3)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.0.16—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 11× in last 7d / 46× 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-05 09:21 UTCEG score recompute
  5. 2026-08-05 09:21 UTCGHSA enrichment
  6. 2026-08-04 15:07 UTCEPSS rescore
  7. 2026-08-04 10:59 UTCGHSA enrichment
  8. 2026-08-04 09:34 UTCEG score recompute
  9. 2026-08-04 09:34 UTCGHSA enrichment
  10. 2026-08-03 10:33 UTCEPSS rescore
  11. 2026-08-02 02:24 UTCEPSS rescore
  12. 2026-08-01 04:13 UTCEPSS rescore
  13. 2026-08-01 04:13 UTCEPSS rescore
  14. 2026-07-30 16:25 UTCEPSS rescore
  15. 2026-07-30 01:28 UTCEPSS rescore
  16. 2026-07-26 14:52 UTCEPSS rescore
  17. 2026-07-26 14:52 UTCEPSS rescore
  18. 2026-07-25 14:16 UTCEPSS rescore
  19. 2026-07-24 14:15 UTCEPSS rescore
  20. 2026-07-23 20:11 UTCOSV refresh
  21. 2026-07-23 14:16 UTCEPSS rescore
  22. 2026-07-23 14:16 UTCEPSS rescore
  23. 2026-07-23 02:17 UTCEG score recompute
  24. 2026-07-22 23:04 UTCEG score recompute
  25. 2026-07-22 14:06 UTCEPSS rescore
Show 75 more
  1. 2026-07-22 14:06 UTCEPSS rescore
  2. 2026-07-21 15:23 UTCEPSS rescore
  3. 2026-07-21 15:23 UTCEPSS rescore
  4. 2026-07-20 17:05 UTCEPSS rescore
  5. 2026-07-19 14:29 UTCEPSS rescore
  6. 2026-07-19 14:29 UTCEPSS rescore
  7. 2026-07-18 10:03 UTCEPSS rescore
  8. 2026-07-18 10:03 UTCEPSS rescore
  9. 2026-07-16 17:00 UTCEPSS rescore
  10. 2026-07-15 16:56 UTCEPSS rescore
  11. 2026-07-15 16:56 UTCEPSS rescore
  12. 2026-07-15 01:58 UTCEPSS rescore
  13. 2026-07-15 01:58 UTCEPSS rescore
  14. 2026-07-13 22:28 UTCEPSS rescore
  15. 2026-07-13 22:28 UTCEPSS rescore
  16. 2026-07-13 06:11 UTCEPSS rescore
  17. 2026-07-13 06:11 UTCEPSS rescore
  18. 2026-07-12 05:44 UTCEPSS rescore
  19. 2026-07-11 08:25 UTCEPSS rescore
  20. 2026-07-11 08:25 UTCEPSS rescore
  21. 2026-07-09 19:08 UTCEPSS rescore
  22. 2026-07-08 15:13 UTCEPSS rescore
  23. 2026-07-07 13:44 UTCEPSS rescore
  24. 2026-07-06 16:25 UTCEPSS rescore
  25. 2026-07-06 14:41 UTCOSV refresh
  26. 2026-07-06 02:21 UTCEPSS rescore
  27. 2026-07-05 02:28 UTCEPSS rescore
  28. 2026-07-04 06:29 UTCEPSS rescore
  29. 2026-07-01 15:04 UTCEPSS rescore
  30. 2026-06-30 23:21 UTCEPSS rescore
  31. 2026-06-30 23:20 UTCEPSS rescore
  32. 2026-06-29 14:04 UTCEPSS rescore
  33. 2026-06-28 14:06 UTCEPSS rescore
  34. 2026-06-28 04:54 UTCEPSS rescore
  35. 2026-06-28 04:54 UTCEPSS rescore
  36. 2026-06-27 03:07 UTCEPSS rescore
  37. 2026-06-27 03:07 UTCEPSS rescore
  38. 2026-06-25 13:48 UTCEPSS rescore
  39. 2026-06-25 13:48 UTCEPSS rescore
  40. 2026-06-24 14:03 UTCEPSS rescore
  41. 2026-06-24 14:03 UTCEPSS rescore
  42. 2026-06-23 21:31 UTCEPSS rescore
  43. 2026-06-23 21:31 UTCEPSS rescore
  44. 2026-06-22 14:24 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 17:51 UTCEPSS rescore
  50. 2026-06-18 17:51 UTCEPSS rescore
  51. 2026-06-18 03:05 UTCOSV refresh
  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

Related CVEs(same product)

Frequently asked(5)

What is CVE-2022-50270?
CVE-2022-50270 is a high vulnerability published on September 15, 2025. In the Linux kernel, the following vulnerability has been resolved: f2fs: fix the assign logic of iocb commit 18ae8d12991b ("f2fs: show more DIO information in tracepoint") introduces iocb field in 'f2fsdirectIO_enter' trace event And it only assigns the pointer and later it accesses its field in…
When was CVE-2022-50270 disclosed?
CVE-2022-50270 was first published in the National Vulnerability Database on September 15, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-50270 actively exploited?
CVE-2022-50270 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.6% of all scored CVEs.
What is the CVSS score of CVE-2022-50270?
CVE-2022-50270 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2022-50270?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50270, 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-50270

Explore →

Is Your Infrastructure Affected by CVE-2022-50270?

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

Start Free Scan →Browse All CVEs