ovpn: fix use after free in unlock_ovpn()
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.427.1.67.2In the Linux kernel, the following vulnerability has been resolved:
ovpn: fix use after free in unlock_ovpn()
unlock_ovpn() iterates over the release_list using llist_for_each_entry() and drops the peer reference inside the loop body via ovpn_peer_put().
If this drops the last reference, the peer is eventually freed. However, llist_for_each_entry() reads peer->release_entry.next in the loop advance expression, which runs after the body. By that time the peer may have already been freed, resulting in a use after free when advancing to the next list entry.
Fix this by using llist_for_each_entry_safe(), which caches the next pointer before executing the loop body.
From the CVE record · Linux
The Linux kernel’s ovpn code can access a freed peer while advancing through a release list in unlock_ovpn(). The input does not specify how an attacker could trigger this, whether access or user interaction is required, or what impact exploitation could have.
Engineers running Linux kernels with the ovpn component should check their versions; affected versions are not specified.