CVE-2025-21863

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-03-12. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

A fix is available — apply it.

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

io_uring: prevent opcode speculation

sqe->opcode is used for different tables, make sure we santitise it against speculations.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
—
EPSS
13.1%
KEV
Not listed

Published

March 12, 2025

Last Modified

June 19, 2026

Advisory Details (6)

Auto-updated Jun 6, 2026
No patch confirmed yet.
generic

io_uring: prevent opcode speculation - kernel/git/stable/linux.git - Linux kernel stable tree

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

io_uring: prevent opcode speculation - kernel/git/stable/linux.git - Linux kernel stable tree

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

io_uring: prevent opcode speculation - kernel/git/stable/linux.git - Linux kernel stable tree

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

io_uring: prevent opcode speculation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/506b9b5e8c2d2a411ea8fe361333f5081c56d23a
generic

io_uring: prevent opcode speculation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1e988c3fe1264708f4f92109203ac5b1d65de50b
generic

io_uring: prevent opcode speculation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/18eae8420081ef8e043ad455937bfb470ef08607

Vendor Advisories for CVE-2025-21863(5)

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

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-78.78) @ noble2026-05-30ubuntu
ubuntulinux-tools-aws (6.11.0-1014.15) @ oracular2026-05-30ubuntu
ubuntulinux-tools-oracle-64k (6.11.0-1016.17) @ oracular2026-05-30ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1033.33) @ noble2026-05-30ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2028.29) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-nvidia-lts-24.04 (6.8.0-1022.23) @ noble2026-05-30ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1035.39) @ noble2026-05-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-26.26) @ oracular2026-05-30ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1032.33) @ noble2026-05-30ubuntu
redhatkernel-0:5.14.0-570.84.1.el9_62026-02-02redhat
redhatkernel-0:5.14.0-611.5.1.el9_72025-11-11redhat
redhatkernel-0:6.12.0-124.8.1.el10_12025-11-11redhat

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.

Additional Vendor Advisories

(9)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× 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.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2025-21863?
CVE-2025-21863 is a high vulnerability published on March 12, 2025. In the Linux kernel, the following vulnerability has been resolved: io_uring: prevent opcode speculation sqe->opcode is used for different tables, make sure we santitise it against speculations.
When was CVE-2025-21863 disclosed?
CVE-2025-21863 was first published in the National Vulnerability Database on March 12, 2025, with the most recent update on June 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-21863 actively exploited?
CVE-2025-21863 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 13.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-21863?
CVE-2025-21863 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-21863?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-21863, 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-2025-21863

Explore →

Is Your Infrastructure Affected by CVE-2025-21863?

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

Start Free Scan →Browse All CVEs