{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97934 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97934 is a memory corruption vulnerability in Linux, published on 25 Sep 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-97934 and fix it if it is affected.\n\nWhat it is: CVE-2026-97934 is a memory corruption vulnerability in Linux, published on 25 Sep 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-97934 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-97934/ (Markdown: https://insights.sbomify.com/CVE-2026-97934/index.md)","id":"CVE-2026-97934","markdown":"https://insights.sbomify.com/CVE-2026-97934/index.md","name":"CVE-2026-97934","record":{"aliases":["AZL-104768","BELL-CVE-2026-97934","DEBIAN-CVE-2026-97934","GHSA-3wpw-vmp3-5ppq","UBUNTU-CVE-2026-97934"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker with tracing access can trigger memory corruption and kernel panic via a specific histogram key configuration.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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 memory corruption from a \"STACKTRACE\" histogram key\n\n\"cpu\", \"CPU\", \"stacktrace\" and \"STACKTRACE\" are generic fields, defined\nwith an offset and a size of zero so that the filter code can match them\nby name. parse_field() maps them onto their common_* equivalents for\nbackward compatibility, but unlike the common_* names it hands the\nplaceholder back to the caller instead of NULL.\n\ncreate_hist_field() takes a non-NULL field as a promise that the record\ncarries a stacktrace and picks HIST_FIELD_FN_STACK, so the __data_loc\nword is read from offset 0, that is from common_type, and its low 16\nbits are followed as an offset into the record. What is found there\nbecomes the length of an unbounded memcpy. Pick an event whose id is\nsmall enough that the offset stays inside its own record and the length\nis a kernel text address:\n\n  # cd /sys/kernel/tracing\n  # echo 'hist:keys=STACKTRACE' \u003e events/ftrace/print/trigger\n  # echo hello \u003e trace_marker\n\n  Oops: general protection fault, probably for non-canonical address\n  RIP: 0010:rb_next+0x23/0x60\n   \u003c/IRQ\u003e\n  RIP: 0010:memcpy+0xc/0x30\n   event_hist_trigger+0x2e7/0x12c0\n  Kernel panic - not syncing: Fatal exception in interrupt\n\nLeave the field NULL, which is what the comment above the branch says\nthe code does and what common_stacktrace already does. FILTER_CPU and\nFILTER_COMM are left alone, their create_hist_field() branches never\nlook at the field.","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 memory corruption from a \"STACKTRACE\" histogram key","id":"CVE-2026-97934","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"tracing: Set the trace clock before registering the histogram trigger","id":"CVE-2026-97935"},"packages":[],"prev":{"headline":"tracing: Take trace_array reference when opening a tracer options file","id":"CVE-2026-97933"},"products":["Linux"],"published":"2026-09-25","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-21","vendors":["Linux"]},"summary":"A local attacker with tracing access can trigger memory corruption and kernel panic via a specific histogram key configuration.","url":"https://insights.sbomify.com/CVE-2026-97934/"}