{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68121 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68121 is a high-severity 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-68121 and fix it if it is affected.\n\nWhat it is: CVE-2026-68121 is a high-severity 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-68121 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-68121/ (Markdown: https://insights.sbomify.com/CVE-2026-68121/index.md)","id":"CVE-2026-68121","markdown":"https://insights.sbomify.com/CVE-2026-68121/index.md","name":"CVE-2026-68121","record":{"aliases":["BELL-CVE-2026-68121","DEBIAN-CVE-2026-68121","GHSA-7hvc-v975-w6v4","UBUNTU-CVE-2026-68121"],"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","requires_auth":"low_privilege","summary":"A use-after-free vulnerability in the Linux kernel PPPoE module allows attackers to execute arbitrary code or escalate privileges via crafted network packets.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\npppoe: reload header pointer after dev_hard_header()\n\npppoe_sendmsg() saves a pointer to the PPPoE header before calling\ndev_hard_header(). Device header callbacks are allowed to reallocate the\nskb head, invalidating pointers into it.\n\nThis can happen when a send is blocked in copy_from_user() while the first\nnon-Ethernet port is added to an empty team device. The team's delegated\nGRE header callback then expands the skb head. PPPoE subsequently writes\nsix bytes through the stale pointer into the freed head.\n\nReload the PPPoE header through the skb's network-header offset after\ndevice header creation. pskb_expand_head() updates that offset when it\nrelocates the head.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-09-18","github_poc":3,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-09-18T10:09:10Z","kind":"github_poc","ref":"https://github.com/suominen/pppoeject","stars":0,"title":"Tracking PPPoEject (CVE-2026-68121), the Linux kernel PPPoE sendmsg use-after-free"},{"date":"2026-09-19T16:28:47Z","kind":"github_poc","ref":"https://github.com/0xredash/CVE-2026-68121","stars":0,"title":"CVE-2026-68121"},{"date":"2026-09-21T02:34:54Z","kind":"github_poc","ref":"https://github.com/HORKimhab/CVE-2026-68121","stars":0,"title":"CVE-2026-68121 PPPoEject"}],"tier":"poc_unverified"},"has_fix":true,"headline":"pppoe: reload header pointer after dev_hard_header()","id":"CVE-2026-68121","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"ovpn: fix peer refcount leak in TCP error paths","id":"CVE-2026-68122"},"packages":[],"prev":{"headline":"rtase: Workaround for TX hang caused by hardware packet parsing","id":"CVE-2026-68120"},"products":["Linux"],"published":"2026-08-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A use-after-free vulnerability in the Linux kernel PPPoE module allows attackers to execute arbitrary code or escalate privileges via crafted network packets.","url":"https://insights.sbomify.com/CVE-2026-68121/"}