CVE-2026-23229

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: virtio - Add spinlock protection with virtqueue notification

When VM boots with one virtio-crypto PCI device and builtin backend, run openssl benchmark command with multiple processes, such as openssl speed -evp aes-128-cbc -engine afalg -seconds 10 -multi 32

openssl processes will hangup and there is error reported like this: virtio_crypto virtio0: dataq.0:id 3 is not a head!

It seems that the data virtqueue need protection when it is handled for virtio done notification. If the spinlock protection is added in virtcrypto_done_task(), openssl benchmark with multiple processes works well.

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 Aug 7, 2026
No patch confirmed yet.
generic

SSA-253495

https://cert-portal.siemens.com/productcert/html/ssa-253495.html
generic

crypto: virtio - Add spinlock protection with virtqueue notification - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: virtio - Add spinlock protection with virtqueue notification - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: virtio - Add spinlock protection with virtqueue notification - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: virtio - Add spinlock protection with virtqueue notification - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: virtio - Add spinlock protection with virtqueue notification - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: virtio - Add spinlock protection with virtqueue notification - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: virtio - Add spinlock protection with virtqueue notification - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/552475d0b6cece73a52c0fa5faa0ce45e99df74b
generic

crypto: virtio - Add spinlock protection with virtqueue notification - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/49c57c6c108931a914ed94e3c0ddb974008260a3

Vendor Advisories for CVE-2026-23229(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.251—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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (49 versions)5.10.251-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.162-1~deb11u1 (15 versions)6.1.164-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (47 versions)6.1.164-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.73-1~bpo12+1 (12 versions)6.12.73-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (101 versions)6.18.12-1—

All Vendor Advisories

(24)

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 / 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 159 total refreshes for this CVE.

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

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2026-23229?
CVE-2026-23229 is a medium vulnerability published on February 18, 2026. In the Linux kernel, the following vulnerability has been resolved: crypto: virtio - Add spinlock protection with virtqueue notification When VM boots with one virtio-crypto PCI device and builtin backend, run openssl benchmark command with multiple processes, such as openssl speed -evp aes-128-cbc…
When was CVE-2026-23229 disclosed?
CVE-2026-23229 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-23229 actively exploited?
CVE-2026-23229 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.4% of all scored CVEs.
What is the CVSS score of CVE-2026-23229?
CVE-2026-23229 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-23229?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23229, 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-2026-23229

Explore →

Is Your Infrastructure Affected by CVE-2026-23229?

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

Start Free Scan →Browse All CVEs