CVE-2023-53996

CRITICALPre-NVD 9.39.3—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
9.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.3Exploit: None knownExposed: 0

A fix is available — apply it.

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

x86/sev: Make enc_dec_hypercall() accept a size instead of npages

enc_dec_hypercall() accepted a page count instead of a size, which forced its callers to round up. As a result, non-page aligned vaddrs caused pages to be spuriously marked as decrypted via the encryption status hypercall, which in turn caused consistent corruption of pages during live migration. Live migration requires accurate encryption status information to avoid migrating pages from the wrong perspective.

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

Published

December 24, 2025

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated Sep 14, 2026
No patch confirmed yet.
generic

x86/sev: Make enc_dec_hypercall() accept a size instead of npages - kernel/git/stable/linux.git - Linux kernel stable tree

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

x86/sev: Make enc_dec_hypercall() accept a size instead of npages - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8ae7457e71a320867d868f2622d7c643596e4f43
generic

x86/sev: Make enc_dec_hypercall() accept a size instead of npages - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6615212d8e131b45bd9705b0d69cc0d2f624666f
generic

x86/sev: Make enc_dec_hypercall() accept a size instead of npages - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ba50e7773a99a109a1ea6f753b766a080d3b21cc

Vendor Advisories for CVE-2023-53996(4)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:4.18.0-553.el8_102024-05-22redhat
redhatkernel-0:4.18.0-477.43.1.el8_82024-01-30redhat
redhatkernel-0:5.14.0-362.13.1.el9_32023-12-12redhat
linuxKernel @ 6.1.53—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 rangeFixed inDependents
linux6.1.27-1 ... 6.1.55-1~bpo11+1 (10 versions)6.1.55-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.5.3-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.5.3-1—

Data Freshness Timeline

(refreshed 5× in last 7d / 25× 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 178 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2023-53996?
CVE-2023-53996 is a critical vulnerability published on December 24, 2025. In the Linux kernel, the following vulnerability has been resolved: x86/sev: Make encdechypercall() accept a size instead of npages encdechypercall() accepted a page count instead of a size, which forced its callers to round up. As a result, non-page aligned vaddrs caused pages to be spuriously…
When was CVE-2023-53996 disclosed?
CVE-2023-53996 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-2023-53996 actively exploited?
CVE-2023-53996 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 98.7% of all scored CVEs.
What is the CVSS score of CVE-2023-53996?
CVE-2023-53996 has a CVSS v4.0 base score of 9.3 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2023-53996?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-53996, 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-2023-53996

Explore →

Is Your Infrastructure Affected by CVE-2023-53996?

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

Start Free Scan →Browse All CVEs