CVE-2026-23222

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-02-18. 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%CVSS: 5.5Exploit: 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:

crypto: omap - Allocate OMAP_CRYPTO_FORCE_COPY scatterlists correctly

The existing allocation of scatterlists in omap_crypto_copy_sg_lists() was allocating an array of scatterlist pointers, not scatterlist objects, resulting in a 4x too small allocation.

Use sizeof(*new_sg) to get the correct object size.

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

Published

February 18, 2026

Last Modified

June 17, 2026

Advisory Details (9)

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

crypto: omap - Allocate OMAP_CRYPTO_FORCE_COPY scatterlists correctly - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: omap - Allocate OMAP_CRYPTO_FORCE_COPY scatterlists correctly - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: omap - Allocate OMAP_CRYPTO_FORCE_COPY scatterlists correctly - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/953c81941b0ad373674656b8767c00234ebf17ac
generic

crypto: omap - Allocate OMAP_CRYPTO_FORCE_COPY scatterlists correctly - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/79f95b51d4278044013672c27519ae88d07013d8
generic

crypto: omap - Allocate OMAP_CRYPTO_FORCE_COPY scatterlists correctly - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6edf8df4bd29f7bfd245b67b2c31d905f1cfc14b
generic

crypto: omap - Allocate OMAP_CRYPTO_FORCE_COPY scatterlists correctly - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/31aff96a41ae6f1f1687c065607875a27c364da8
generic

crypto: omap - Allocate OMAP_CRYPTO_FORCE_COPY scatterlists correctly - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2ed27b5a1174351148c3adbfc0cd86d54072ba2e
generic

crypto: omap - Allocate OMAP_CRYPTO_FORCE_COPY scatterlists correctly - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1562b1fb7e17c1b3addb15e125c718b2be7f5512

Vendor Advisories for CVE-2026-23222(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.10.251osv

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.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-23222?
CVE-2026-23222 is a medium vulnerability published on February 18, 2026. In the Linux kernel, the following vulnerability has been resolved: crypto: omap - Allocate OMAPCRYPTOFORCE_COPY scatterlists correctly The existing allocation of scatterlists in omapcryptocopysglists() was allocating an array of scatterlist pointers, not scatterlist objects, resulting in a 4x too…
When was CVE-2026-23222 disclosed?
CVE-2026-23222 was first published in the National Vulnerability Database on February 18, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23222 actively exploited?
CVE-2026-23222 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 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-23222?
CVE-2026-23222 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-23222?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23222, 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-2026-23222

Explore →

Is Your Infrastructure Affected by CVE-2026-23222?

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