ovpn: defer key slot crypto freeing to workqueue
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.577.1.107.2In the Linux kernel, the following vulnerability has been resolved:
ovpn: defer key slot crypto freeing to workqueue
Key slots are released through a kref and the existing release path frees the AEAD transforms from an RCU callback. That is not safe for all crypto implementations: crypto_free_aead can sleep, for example when an async or hardware implementation has teardown work to complete.
Use queue_rcu_work for key-slot release. This keeps the RCU grace period needed by lockless key-slot readers, but runs the actual crypto teardown from workqueue context where sleeping is allowed. Once the rcu_work callback runs, pre-existing RCU readers are gone, and the final kref put already proves that no transform user remains, so the worker can release the AEAD transforms and free the slot directly.
The previous patch drains ovpn_wq during module exit, so queued key-slot teardown work cannot outlive module text.
From the CVE record · Linux
The Linux kernel’s ovpn key-slot release path can free AEAD transforms from an RCU callback, where sleeping is unsafe for some crypto implementations. The input does not specify what an attacker could do or whether exploitation requires network access, authentication, local access, or user interaction.
Engineers running Linux kernels with ovpn should check their versions; affected versions are not specified.