ovpn: fix use after free in unlock_ovpn()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 4cdb209f12a89c5faf9be0c45edb90ccdf65db0c, Kernel 5b96227c0e8b212b74838424c929fc889aedb555 and Kernel e1ad6fe5db719874efa45b2caf9934552e09fc43.
In 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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.16, >=80747caef33d77f5c1b3d24644e6d7dae69066b5 <4cdb209f12a89c5faf9be0c45edb90ccdf65db0c, >=80747caef33d77f5c1b3d24644e6d7dae69066b5 <5b96227c0e8b212b74838424c929fc889aedb555, >=80747caef33d77f5c1b3d24644e6d7dae69066b5 <e1ad6fe5db719874efa45b2caf9934552e09fc43 | 4cdb209f12a89c5faf9be0c45edb90ccdf65db0c, 5b96227c0e8b212b74838424c929fc889aedb555, e1ad6fe5db719874efa45b2caf9934552e09fc43 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket