CVE-2026-23229

See a problem?
Please try reporting it to the source first.
Source
https://cve.org/CVERecord?id=CVE-2026-23229
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-23229.json
JSON Data
https://api.test.osv.dev/v1/vulns/CVE-2026-23229
Downstream
Related
Published
2026-02-18T14:53:33.015Z
Modified
2026-05-15T11:54:21.824123658Z
Summary
crypto: virtio - Add spinlock protection with virtqueue notification
Details

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 virtcryptodonetask(), openssl benchmark with multiple processes works well.

Database specific 
{
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23229.json",
    "cna_assigner": "Linux"
}
References

Affected packages

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
5.10.251
Type
ECOSYSTEM
Events
Introduced
5.11.0
Fixed
5.15.201
Type
ECOSYSTEM
Events
Introduced
5.16.0
Fixed
6.1.164
Type
ECOSYSTEM
Events
Introduced
6.2.0
Fixed
6.6.125
Type
ECOSYSTEM
Events
Introduced
6.7.0
Fixed
6.12.72
Type
ECOSYSTEM
Events
Introduced
6.8.0
Fixed
6.18.11
Type
ECOSYSTEM
Events
Introduced
6.13.0
Fixed
6.19.1

Database specific

source 
"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-23229.json"