{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68174 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68174 is a 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-68174 and fix it if it is affected.\n\nWhat it is: CVE-2026-68174 is a 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-68174 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-68174/ (Markdown: https://insights.sbomify.com/CVE-2026-68174/index.md)","id":"CVE-2026-68174","markdown":"https://insights.sbomify.com/CVE-2026-68174/index.md","name":"CVE-2026-68174","record":{"aliases":["BELL-CVE-2026-68174","DEBIAN-CVE-2026-68174","GHSA-c2f7-rhw7-9m5r","UBUNTU-CVE-2026-68174"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel tracing","requires_auth":"low_privilege","summary":"A local attacker with low privileges can cause a kernel crash by triggering a null pointer dereference in the Linux kernel tracing subsystem via dynamic events.","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\ntracing: Fix union collision of module and refcnt for dynamic events\n\nIn 'struct trace_event_call', the 'module' pointer and the 'refcnt'\natomic variable share the same memory space in a union. For dynamic\nevents, the union member is 'refcnt', which acts as an active\nreference counter.\n\nWhen a dynamic event (such as kprobe, uprobe, fprobe, eprobe, or\nwprobe) has a non-zero reference count (e.g. due to active event\ntriggers or perf attachments), its 'call-\u003emodule' evaluates to a\nsmall non-zero integer instead of NULL.\n\nWhen filtering or setting events for a specific module (e.g., writing\n':mod:\u003cmodule\u003e' to 'set_event'), the code in\n'__ftrace_set_clr_event_nolock()' and 'update_event_fields()' reads\n'call-\u003emodule' directly without checking whether the event is dynamic.\nThis causes the kernel to treat the small integer (refcnt) as a\n'struct module' pointer, leading to a NULL/invalid pointer dereference\n(Oops) when dereferencing the module name.\n\nFix this by ensuring that the 'TRACE_EVENT_FL_DYNAMIC' flag is checked\nbefore treating 'call-\u003emodule' as a valid pointer in these code paths.","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":"tracing: Fix union collision of module and refcnt for dynamic events","id":"CVE-2026-68174","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"tracing: Fix resource leak on mmiotrace trace_pipe close","id":"CVE-2026-68175"},"packages":[],"prev":{"headline":"ublk: wait on ublk_dev_ready() instead of ub-\u003ecompletion","id":"CVE-2026-68173"},"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 local attacker with low privileges can cause a kernel crash by triggering a null pointer dereference in the Linux kernel tracing subsystem via dynamic events.","url":"https://insights.sbomify.com/CVE-2026-68174/"}