{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97921 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97921 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-97921 and fix it if it is affected.\n\nWhat it is: CVE-2026-97921 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-97921 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-97921/ (Markdown: https://insights.sbomify.com/CVE-2026-97921/index.md)","id":"CVE-2026-97921","markdown":"https://insights.sbomify.com/CVE-2026-97921/index.md","name":"CVE-2026-97921","record":{"aliases":["AZL-104810","BELL-CVE-2026-97921","DEBIAN-CVE-2026-97921","GHSA-v583-2w7f-r9gc","UBUNTU-CVE-2026-97921"],"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 memory leak in the Linux kernel tracing subsystem allows local attackers to exhaust kernel memory by repeatedly writing invalid histogram triggers.","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: Free histogram the field rejected for a bad modifier\n\nWriting a hist trigger whose value or variable carries a modifier that is\nnot allowed there leaks the fields that were built for it.\n\n__create_val_field() takes the field from parse_expr() and stores it in\nhist_data-\u003efields[] only after the modifier checks have run:\n\n\thist_field = parse_expr(hist_data, file, field_str, flags, var_name,\n\t\t\t\t\u0026n_subexprs);\n\t...\n\tif (hist_field-\u003eflags \u0026 HIST_FIELD_FL_VAR) {\n\t\tif (hist_field-\u003eflags \u0026 (...))\n\t\t\tgoto err;\n\t} else {\n\t\tif (hist_field-\u003eflags \u0026 (...))\n\t\t\tgoto err;\n\t}\n\n\thist_data-\u003efields[val_idx] = hist_field;\n\nBoth checks jump past that store, and the err label returns without\nfreeing anything. The error unwinds to create_hist_data(), which calls\ndestroy_hist_data() -\u003e destroy_hist_fields(), and that reaches a field\nonly by walking fields[]. A field that never got there is unreachable.\n\ncommit e0213434fe3e (\"tracing: Do not let histogram values have some\nmodifiers\") set ret to -EINVAL and fell through to the store, which left\nthe field owned by fields[] and freed along with the rest of hist_data.\nSplitting the check into a value case and a variable case replaced that\nfall-through with a goto that skips it.\n\nWith CONFIG_DEBUG_KMEMLEAK, 200 writes of\n\n  # echo 'hist:keys=prev_pid:vals=next_pid.log2' \u003e \\\n\t events/sched/sched_switch/trigger\n\neach correctly rejected with -EINVAL, leave 332 unreferenced objects\n(63744 bytes) reported at create_hist_field(); 200 install and remove\ncycles of a valid trigger leave none. A '.log2' field is two\nallocations, since create_hist_field() puts the plain field in\noperands[0] of the log2 field, and both are reported.\n\nUse destroy_hist_field() rather than __destroy_hist_field() so that\noperands[0] is freed as well. It returns early for HIST_FIELD_FL_VAR_REF,\nwhich is what an operand owned by hist_data-\u003evar_refs[] needs; the\nrejected field itself is never a var ref, because a var ref never carries\na modifier flag.","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: Free histogram the field rejected for a bad modifier","id":"CVE-2026-97921","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"tracing: Free histogram var refs regardless of how often they are referenced","id":"CVE-2026-97922"},"packages":[],"prev":{"headline":"tracing: Keep the entry count when the histogram stats allocation fails","id":"CVE-2026-97920"},"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-19","vendors":["Linux"]},"summary":"A memory leak in the Linux kernel tracing subsystem allows local attackers to exhaust kernel memory by repeatedly writing invalid histogram triggers.","url":"https://insights.sbomify.com/CVE-2026-97921/"}