{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98268 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98268 is a vulnerability in Linux, published on 6 Oct 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-98268 and fix it if it is affected.\n\nWhat it is: CVE-2026-98268 is a vulnerability in Linux, published on 6 Oct 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-98268 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-98268/ (Markdown: https://insights.sbomify.com/CVE-2026-98268/index.md)","id":"CVE-2026-98268","markdown":"https://insights.sbomify.com/CVE-2026-98268/index.md","name":"CVE-2026-98268","record":{"aliases":["DEBIAN-CVE-2026-98268","GHSA-47g9-qxgv-4q29","UBUNTU-CVE-2026-98268"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can cause a kernel crash via null pointer dereference in perf subsystem during module unload with active connections.","user_interaction":"not_required","vuln_class":"null_dereference"},"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\nperf: Fix null pointer access in is_include_guest_event()\n\nA typical module unload occurring event when there is an active perf\nconnection leads to freeing of the pmu pointer. The call log is something\nlike:\n ..\n __pmu_detach_event\n pmu_detach_event\n pmu_detach_events\n perf_pmu_unregister\n ..\n\n__pmu_detach_event() sets event-\u003epmu to null. When the perf connection\nfinally is closed, the following stack trace is observed:\n\n Oops: general protection fault, kernel NULL pointer dereference\n ...\n RIP: 0010:_free_event+0x3e/0x370\n ...\n Call Trace:\n ...\n perf_event_release_kernel+0x260/0x2d0\n perf_release+0x12/0x20\n\nA call to mediated_pmu_unaccount_event() inside _free_event() is the root\ncause of this crash. Adding a check inside is_include_guest_event() ensures\nwe don't accidentally access a null pmu ptr. In addition to this, we will\nnow call mediated_pmu_unaccount_event() before clearing the pmu ptr so that\nnr_include_guest_events counts are maintained correctly.","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":"perf: Fix null pointer access in is_include_guest_event()","id":"CVE-2026-98268","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"btrfs: abort transaction on failure to update inode for hole punching and reflinking","id":"CVE-2026-98269"},"packages":[],"prev":{"headline":"9p: Fix v9fs_issue_write() to update i_size and remote_i_size","id":"CVE-2026-98267"},"products":["Linux"],"published":"2026-10-06","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-10-19","vendors":["Linux"]},"summary":"A local attacker can cause a kernel crash via null pointer dereference in perf subsystem during module unload with active connections.","url":"https://insights.sbomify.com/CVE-2026-98268/"}