{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68342 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68342 is an use after free vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-68342 and fix it if it is affected.\n\nWhat it is: CVE-2026-68342 is an use after free vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-68342 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-68342/ (Markdown: https://insights.sbomify.com/CVE-2026-68342/index.md)","id":"CVE-2026-68342","markdown":"https://insights.sbomify.com/CVE-2026-68342/index.md","name":"CVE-2026-68342","record":{"aliases":["BELL-CVE-2026-68342","DEBIAN-CVE-2026-68342","GHSA-wh63-3892-rjx3","UBUNTU-CVE-2026-68342"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel OVPN","requires_auth":"low_privilege","summary":"A use-after-free in the Linux kernel OVPN module allows local attackers to execute code or escalate privileges via socket release race conditions.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\novpn: avoid putting unrelated P2P peer on socket release\n\novpn_peer_release_p2p() is called when an OVPN UDP socket is being\ndestroyed. It checks the currently published P2P peer and releases it only\nif that peer still uses the socket being destroyed.\n\nA peer replacement can publish a new peer before the old UDP socket is\ndestroyed. When the old socket destruction path runs afterwards,\novpn_peer_release_p2p() observes the new peer through ovpn-\u003epeer. Since the\nnew peer uses a different socket, the function takes the socket mismatch\nbranch.\n\nThat branch still calls ovpn_peer_put(peer). At this point, however, peer\nis the currently published replacement peer, not the peer associated with\nthe socket being destroyed. Dropping its reference can free it while\novpn-\u003epeer still points to it, leading to later use-after-free accesses\nfrom the peer and socket cleanup paths.\n\nKASAN reports this as a slab-use-after-free on the kmalloc-1k ovpn_peer\nobject. In the reproducer, the object is allocated from ovpn_peer_new() via\novpn_nl_peer_new_doit(), and freed through ovpn_peer_release_rcu() from RCU\ncallback processing. Observed access sites include ovpn_peer_remove(),\novpn_socket_release(), ovpn_nl_peer_del_notify(), and unlock_ovpn().\n\nFix this by returning from the socket mismatch branch without putting the\npeer.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"ovpn: avoid putting unrelated P2P peer on socket release","id":"CVE-2026-68342","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"smb: client: validate DFS referral PathConsumed","id":"CVE-2026-68343"},"packages":[],"prev":{"headline":"ovpn: fix use after free in unlock_ovpn()","id":"CVE-2026-68341"},"products":["Linux"],"published":"2026-08-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"A use-after-free in the Linux kernel OVPN module allows local attackers to execute code or escalate privileges via socket release race conditions.","url":"https://insights.sbomify.com/CVE-2026-68342/"}