CVE-2022-49559

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.3%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

KVM: x86: Drop WARNs that assert a triple fault never "escapes" from L2

Remove WARNs that sanity check that KVM never lets a triple fault for L2 escape and incorrectly end up in L1. In normal operation, the sanity check is perfectly valid, but it incorrectly assumes that it's impossible for userspace to induce KVM_REQ_TRIPLE_FAULT without bouncing through KVM_RUN (which guarantees kvm_check_nested_state() will see and handle the triple fault).

The WARN can currently be triggered if userspace injects a machine check while L2 is active and CR4.MCE=0. And a future fix to allow save/restore of KVM_REQ_TRIPLE_FAULT, e.g. so that a synthesized triple fault isn't lost on migration, will make it trivially easy for userspace to trigger the WARN.

Clearing KVM_REQ_TRIPLE_FAULT when forcibly leaving guest mode is tempting, but wrong, especially if/when the request is saved/restored, e.g. if userspace restores events (including a triple fault) and then restores nested state (which may forcibly leave guest mode). Ignoring the fact that KVM doesn't currently provide the necessary APIs, it's userspace's responsibility to manage pending events during save/restore.

------------[ cut here ]------------ WARNING: CPU: 7 PID: 1399 at arch/x86/kvm/vmx/nested.c:4522 nested_vmx_vmexit+0x7fe/0xd90 [kvm_intel] Modules linked in: kvm_intel kvm irqbypass CPU: 7 PID: 1399 Comm: state_test Not tainted 5.17.0-rc3+ #808 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 RIP: 0010:nested_vmx_vmexit+0x7fe/0xd90 [kvm_intel] Call Trace: vmx_leave_nested+0x30/0x40 [kvm_intel] vmx_set_nested_state+0xca/0x3e0 [kvm_intel] kvm_arch_vcpu_ioctl+0xf49/0x13e0 [kvm] kvm_vcpu_ioctl+0x4b9/0x660 [kvm] __x64_sys_ioctl+0x83/0xb0 do_syscall_64+0x3b/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae ---[ end trace 0000000000000000 ]---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

February 26, 2025

Last Modified

October 22, 2025

References (4)

Vendor Advisories for CVE-2022-49559(2)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-162.6.1.el9_12022-11-15redhat
redhatkernel-0:4.18.0-425.3.1.el82022-11-08redhat
linuxKernel @ 5.15.45 (fixes >=5.13.0)—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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.18.2-1: fixed in 5.18.2-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.18.2-1: fixed in 5.18.2-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.18.2-1: fixed in 5.18.2-1
—

Data Freshness Timeline

(refreshed 7× 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 164 total refreshes for this CVE.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2022-49559?
CVE-2022-49559 is a medium vulnerability published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Drop WARNs that assert a triple fault never "escapes" from L2 Remove WARNs that sanity check that KVM never lets a triple fault for L2 escape and incorrectly end up in L1. In normal operation, the sanity check is…
When was CVE-2022-49559 disclosed?
CVE-2022-49559 was first published on February 26, 2025, with the most recent update on October 22, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-49559 actively exploited?
CVE-2022-49559 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-49559?
CVE-2022-49559 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-49559?
A fix for CVE-2022-49559 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-49559 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-49559

Explore →

Is Your Infrastructure Affected by CVE-2022-49559?

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

Book a Demo →Browse All CVEs