GHSA-998J-MXM9-VQXJ

Vulnerability from github – Published: 2026-08-10 15:33 – Updated: 2026-08-14 00:31
VLAI
Details

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.

Severity
8.8 (High)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2026-68341"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-10T13:20:24Z",
    "severity": "HIGH"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\novpn: fix use after free in unlock_ovpn()\n\nunlock_ovpn() iterates over the release_list using llist_for_each_entry()\nand drops the peer reference inside the loop body via ovpn_peer_put().\n\nIf this drops the last reference, the peer is eventually freed. However,\nllist_for_each_entry() reads peer-\u003erelease_entry.next in the loop advance\nexpression, which runs after the body. By that time the peer may have\nalready been freed, resulting in a use after free when advancing to the\nnext list entry.\n\nFix this by using llist_for_each_entry_safe(), which caches the next\npointer before executing the loop body.",
  "id": "GHSA-998j-mxm9-vqxj",
  "modified": "2026-08-14T00:31:56Z",
  "published": "2026-08-10T15:33:47Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-68341"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/4cdb209f12a89c5faf9be0c45edb90ccdf65db0c"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/5b96227c0e8b212b74838424c929fc889aedb555"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/e1ad6fe5db719874efa45b2caf9934552e09fc43"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.