CVE-2022-50753

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-12-24. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.8EG
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.8Exploit: 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 do sanity check on summary info

As Wenqing Liu reported in bugzilla:

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

BUG: KASAN: use-after-free in recover_data+0x63ae/0x6ae0 [f2fs] Read of size 4 at addr ffff8881464dcd80 by task mount/1013

CPU: 3 PID: 1013 Comm: mount Tainted: G W 6.0.0-rc4 #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014 Call Trace: dump_stack_lvl+0x45/0x5e print_report.cold+0xf3/0x68d kasan_report+0xa8/0x130 recover_data+0x63ae/0x6ae0 [f2fs] f2fs_recover_fsync_data+0x120d/0x1fc0 [f2fs] f2fs_fill_super+0x4665/0x61e0 [f2fs] mount_bdev+0x2cf/0x3b0 legacy_get_tree+0xed/0x1d0 vfs_get_tree+0x81/0x2b0 path_mount+0x47e/0x19d0 do_mount+0xce/0xf0 __x64_sys_mount+0x12c/0x1a0 do_syscall_64+0x38/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd

The root cause is: in fuzzed image, SSA table is corrupted: ofs_in_node is larger than ADDRS_PER_PAGE(), result in out-of-range access on 4k-size page.

  • recover_data
  • do_recover_data
  • check_index_in_prev_nodes
  • f2fs_data_blkaddr

This patch adds sanity check on summary info in recovery and GC flow in where the flows rely on them.

After patch: [ 29.310883] F2FS-fs (loop0): Inconsistent ofs_in_node:65286 in summary, ino:0, nid:6, max:1018

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

Published

December 24, 2025

Last Modified

August 5, 2026

Advisory Details (6)

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

f2fs: fix to do sanity check on summary info - kernel/git/stable/linux.git - Linux kernel stable tree

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

f2fs: fix to do sanity check on summary info - kernel/git/stable/linux.git - Linux kernel stable tree

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

f2fs: fix to do sanity check on summary info - kernel/git/stable/linux.git - Linux kernel stable tree

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

f2fs: fix to do sanity check on summary info - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/73687c53919f49dff3852155621dab7a35c52854
generic

f2fs: fix to do sanity check on summary info - kernel/git/stable/linux.git - Linux kernel stable tree

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

f2fs: fix to do sanity check on summary info - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0922ad64ccefa3e483e84355942b86e13c8fea68

Vendor Advisories for CVE-2022-50753(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.4.220—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 (22 versions)5.10.158-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—6.0.3-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.0.3-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.0.3-1—

Data Freshness Timeline

(refreshed 3× in last 7d / 23× 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 200 total refreshes for this CVE.

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

Related CVEs(same product)

Frequently asked(5)

What is CVE-2022-50753?
CVE-2022-50753 is a high vulnerability published on December 24, 2025. In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on summary info As Wenqing Liu reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=216456 BUG: KASAN: use-after-free in recover_data+0x63ae/0x6ae0 [f2fs] Read of size 4 at addr…
When was CVE-2022-50753 disclosed?
CVE-2022-50753 was first published in the National Vulnerability Database on December 24, 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-50753 actively exploited?
CVE-2022-50753 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 89.4% of all scored CVEs.
What is the CVSS score of CVE-2022-50753?
CVE-2022-50753 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2022-50753?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50753, 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-50753

Explore →

Is Your Infrastructure Affected by CVE-2022-50753?

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

Start Free Scan →Browse All CVEs