Answer in brief
CVE-2026-68341 records a High severity (CVSS 8.8) vulnerability in ovpn: fix use after free in unlock_ovpn(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=80747caef33d77f5c1b3d24644e6d7dae69066b5 <5b96227c0e8b212b74838424c929fc889aedb555 || >=80747caef33d77f5c1b3d24644e6d7dae69066b5 <4cdb209f12a89c5faf9be0c45edb90ccdf65db0c || >=80747caef33d77f5c1b3d24644e6d7dae69066b5 <e1ad6fe5db719874efa45b2caf9934552e09fc43 | 5b96227c0e8b212b74838424c929fc889aedb555, 4cdb209f12a89c5faf9be0c45edb90ccdf65db0c, e1ad6fe5db719874efa45b2caf9934552e09fc43 |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.