Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-23229crypto: virtio - Add spinlock protection with virtqueue notification

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 36 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-23229, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.14% · top 96% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 0eb69890e86775d178452880ea0d24384c5ccedf – < 552475d0b6cece73a52c0fa5faa0ce45e99df74b
    • affected 75cba72ddb788a5b9c7ed2139fbb84383df029eb – < 8ee8ccfd60bf17cbdab91069d324b5302f4f3a30
    • affected ae4747dab2eab95a68bb2f6c7e904bff0424e1b1 – < c9e594194795c86ca753ad6ed64c2762e9309d0d
    • affected c4c54fce9ec54a59a4ca035af13c2823c76684cc – < d6f0d586808689963e58fd739bed626ff5013b24
    • affected fed93fb62e05c38152b0fc1dc9609639e63eed76 – < c0a0ded3bb7fd45f720faa48449a930153257d3a
    • affected fed93fb62e05c38152b0fc1dc9609639e63eed76 – < e69a7b0a71b6561b3b6459f1fded8d589f2e8ac2
    • affected fed93fb62e05c38152b0fc1dc9609639e63eed76 – < 49c57c6c108931a914ed94e3c0ddb974008260a3
    • affected fed93fb62e05c38152b0fc1dc9609639e63eed76 – < b505047ffc8057555900d2d3a005d033e6967382
    • affected 96be18c8fff9d57e29621386e2fa17268383ea27
    • affected 830a4f073f7edd2cc4f30ba95bdc3495d97c2550
    • affected 8862c0d2e47ba1733d9687fe0ff4e02d6e391255
    • affected 5.10.209 – < 5.10.251
    • affected 5.15.148 – < 5.15.201
    • affected 6.1.75 – < 6.1.164
    • affected 6.6.14 – < 6.6.125
    • affected 4.19.306 – < 4.20
    • affected 5.4.268 – < 5.5
    • affected 6.7.2 – < 6.8
  • Linux · Linux

    • affected 6.8
    • unaffected < 6.8
    • unaffected 5.10.251 – ≤ 5.10.*
    • unaffected 5.15.201 – ≤ 5.15.*
    • unaffected 6.1.164 – ≤ 6.1.*
    • unaffected 6.6.125 – ≤ 6.6.*
    • unaffected 6.12.72 – ≤ 6.12.*
    • unaffected 6.18.11 – ≤ 6.18.*
    • unaffected 6.19.1 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-23229 badge
[![CVE-2026-23229](https://cveledger.app/badge/CVE-2026-23229.svg)](https://cveledger.app/cve/CVE-2026-23229)

Record last updated .