CVE-2022-50673

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-12-09. 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

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

ext4: fix use-after-free in ext4_orphan_cleanup

I caught a issue as follows: ================================================================== BUG: KASAN: use-after-free in __list_add_valid+0x28/0x1a0 Read of size 8 at addr ffff88814b13f378 by task mount/710

CPU: 1 PID: 710 Comm: mount Not tainted 6.1.0-rc3-next #370 Call Trace: dump_stack_lvl+0x73/0x9f print_report+0x25d/0x759 kasan_report+0xc0/0x120 __asan_load8+0x99/0x140 __list_add_valid+0x28/0x1a0 ext4_orphan_cleanup+0x564/0x9d0 [ext4] __ext4_fill_super+0x48e2/0x5300 [ext4] ext4_fill_super+0x19f/0x3a0 [ext4] get_tree_bdev+0x27b/0x450 ext4_get_tree+0x19/0x30 [ext4] vfs_get_tree+0x49/0x150 path_mount+0xaae/0x1350 do_mount+0xe2/0x110 __x64_sys_mount+0xf0/0x190 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x63/0xcd [...] ==================================================================

Above issue may happen as follows: ------------------------------------- ext4_fill_super ext4_orphan_cleanup --- loop1: assume last_orphan is 12 --- list_add(&EXT4_I(inode)->i_orphan, &EXT4_SB(sb)->s_orphan) ext4_truncate --> return 0 ext4_inode_attach_jinode --> return -ENOMEM iput(inode) --> free inode<12> --- loop2: last_orphan is still 12 --- list_add(&EXT4_I(inode)->i_orphan, &EXT4_SB(sb)->s_orphan); // use inode<12> and trigger UAF

To solve this issue, we need to propagate the return value of ext4_inode_attach_jinode() appropriately.

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

Published

December 9, 2025

Last Modified

August 5, 2026

Advisory Details (7)

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

ext4: fix use-after-free in ext4_orphan_cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

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

ext4: fix use-after-free in ext4_orphan_cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7908b8a541b1578cc61b4da7f19b604a931441da
generic

ext4: fix use-after-free in ext4_orphan_cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

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

ext4: fix use-after-free in ext4_orphan_cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

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

ext4: fix use-after-free in ext4_orphan_cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7223d5e75f26352354ea2c0ccf8b579821b52adf
generic

ext4: fix use-after-free in ext4_orphan_cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/026a4490b5381229a30f23d073b58e8e35ee6858
generic

ext4: fix use-after-free in ext4_orphan_cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7f801a1593cb957f73659732836b2dafbdfc7709

Vendor Advisories for CVE-2022-50673(14)

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

Patch Availability(14)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:3.10.0-1160.147.1.el72026-03-03redhat
redhatkernel-rt-0:3.10.0-1160.147.1.rt56.1299.el72026-03-03redhat
redhatkernel-0:4.18.0-477.130.1.el8_82026-02-25redhat
redhatkernel-0:4.18.0-305.186.1.el8_42026-02-25redhat
redhatkernel-rt-0:5.14.0-284.158.1.rt14.443.el9_22026-02-25redhat
redhatkernel-0:5.14.0-284.158.1.el9_22026-02-25redhat
redhatkernel-0:4.18.0-193.185.1.el8_22026-02-12redhat
redhatkernel-0:5.14.0-70.165.1.el9_02026-02-11redhat
redhatkernel-rt-0:5.14.0-70.165.1.rt21.237.el9_02026-02-11redhat
redhatkernel-0:4.18.0-372.179.1.el8_62026-02-11redhat
redhatkernel-rt-0:4.18.0-553.104.1.rt7.445.el8_102026-02-10redhat
redhatkernel-0:4.18.0-553.104.1.el8_102026-02-09redhat
redhatkernel-0:5.14.0-427.13.1.el9_42024-04-30redhat
linuxKernel @ 4.19.270—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 (25 versions)5.10.178-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—6.1.4-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.1.4-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.1.4-1—

Data Freshness Timeline

(refreshed 6× in last 7d / 24× 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 194 total refreshes for this CVE.

  1. 2026-09-07 15:59 UTCEPSS rescore
  2. 2026-09-06 13:45 UTCEPSS rescore
  3. 2026-09-05 15:25 UTCEPSS rescore
  4. 2026-09-04 13:57 UTCEPSS rescore
  5. 2026-09-04 05:04 UTCEPSS rescore
  6. 2026-09-02 14:09 UTCEPSS rescore
  7. 2026-09-01 13:51 UTCEPSS rescore
  8. 2026-08-30 19:15 UTCEPSS rescore
  9. 2026-08-30 01:19 UTCEPSS rescore
  10. 2026-08-28 21:38 UTCEPSS rescore
  11. 2026-08-27 14:22 UTCEPSS rescore
  12. 2026-08-26 14:43 UTCEPSS rescore
  13. 2026-08-25 13:46 UTCEPSS rescore
  14. 2026-08-24 12:00 UTCOSV refresh
  15. 2026-08-23 00:17 UTCEPSS rescore
  16. 2026-08-21 23:46 UTCEPSS rescore
  17. 2026-08-19 17:01 UTCEPSS rescore
  18. 2026-08-18 13:45 UTCEPSS rescore
  19. 2026-08-17 13:44 UTCEPSS rescore
  20. 2026-08-16 14:53 UTCEPSS rescore
  21. 2026-08-16 02:12 UTCEPSS rescore
  22. 2026-08-15 01:27 UTCEPSS rescore
  23. 2026-08-13 21:58 UTCEPSS rescore
  24. 2026-08-12 13:48 UTCEPSS rescore
  25. 2026-08-09 13:44 UTCEPSS rescore
Show 75 more
  1. 2026-08-09 13:44 UTCEPSS rescore
  2. 2026-08-08 16:34 UTCEPSS rescore
  3. 2026-08-08 08:03 UTCEG score recompute
  4. 2026-08-08 08:03 UTCVendor advisory
  5. 2026-08-08 08:03 UTCGHSA enrichment
  6. 2026-08-07 16:24 UTCEPSS rescore
  7. 2026-08-06 13:44 UTCEPSS rescore
  8. 2026-08-05 19:15 UTCEPSS rescore
  9. 2026-08-05 09:18 UTCEG score recompute
  10. 2026-08-05 09:18 UTCVendor advisory
  11. 2026-08-05 09:18 UTCGHSA enrichment
  12. 2026-08-04 15:07 UTCEPSS rescore
  13. 2026-08-04 10:52 UTCEG score recompute
  14. 2026-08-04 10:52 UTCVendor advisory
  15. 2026-08-04 10:52 UTCGHSA enrichment
  16. 2026-08-04 10:35 UTCEPSS rescore
  17. 2026-08-04 09:27 UTCEG score recompute▲ 7.80
  18. 2026-08-04 09:27 UTCVendor advisory
  19. 2026-08-04 09:26 UTCGHSA enrichment
  20. 2026-08-04 09:20 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  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-27 05:39 UTCOSV refresh
  29. 2026-07-26 14:52 UTCEPSS rescore
  30. 2026-07-26 14:52 UTCEPSS rescore
  31. 2026-07-25 14:16 UTCEPSS rescore
  32. 2026-07-24 14:15 UTCEPSS rescore
  33. 2026-07-23 14:16 UTCEPSS rescore
  34. 2026-07-23 14:16 UTCEPSS rescore
  35. 2026-07-23 02:17 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-10 00:17 UTCOSV refresh
  61. 2026-07-09 19:08 UTCEPSS rescore
  62. 2026-07-08 15:13 UTCEPSS rescore
  63. 2026-07-07 13:44 UTCEPSS rescore
  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

Frequently asked(5)

What is CVE-2022-50673?
CVE-2022-50673 is a high vulnerability published on December 9, 2025. In the Linux kernel, the following vulnerability has been resolved: ext4: fix use-after-free in ext4orphancleanup I caught a issue as follows: ================================================================== BUG: KASAN: use-after-free in listaddvalid+0x28/0x1a0 Read of size 8 at addr…
When was CVE-2022-50673 disclosed?
CVE-2022-50673 was first published in the National Vulnerability Database on December 9, 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-50673 actively exploited?
CVE-2022-50673 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.0% of all scored CVEs.
What is the CVSS score of CVE-2022-50673?
CVE-2022-50673 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2022-50673?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50673, 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-50673

Explore →

Is Your Infrastructure Affected by CVE-2022-50673?

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

Start Free Scan →Browse All CVEs