CyberRota Analysis
AI-GeneratedThe vulnerability affects the Linux kernel's OpenVPN implementation, specifically in how crypto completion callbacks manage peer and key-slot references. If the peer reference is released prematurely, it can lead to potential use-after-free conditions, allowing for unintentional access to freed memory, which could compromise system stability or security. Organizations utilizing Linux systems with OpenVPN should prioritize addressing this issue to mitigate risks associated with improper memory management.
Original NVD Description
In the Linux kernel, the following vulnerability has been resolved: ovpn: finish crypto callback cleanup before peer release Crypto completion callbacks hold both key-slot and peer references. The peer reference pins the netdev, and dropping the last peer reference can let netdev unregistration and module removal make progress. Do not release that peer reference before the callback has finished its own cleanup. If ovpn_crypto_key_slot_put runs after ovpn_peer_put, it can schedule an RCU callback backed by module text after ovpn_cleanup rcu_barrier has already run. The TX error path also freed the remaining skb after ovpn_peer_put, leaving callback cleanup outside the peer/netdev lifetime window. Release the key slot and free any remaining skb first, then drop the peer reference as the last callback action.