{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97922 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97922 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-97922 and fix it if it is affected.\n\nWhat it is: CVE-2026-97922 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-97922 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-97922/ (Markdown: https://insights.sbomify.com/CVE-2026-97922/index.md)","id":"CVE-2026-97922","markdown":"https://insights.sbomify.com/CVE-2026-97922/index.md","name":"CVE-2026-97922","record":{"aliases":["AZL-104196","BELL-CVE-2026-97922","DEBIAN-CVE-2026-97922","GHSA-m6gp-f257-gxcp","UBUNTU-CVE-2026-97922"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel tracing","requires_auth":"high_privilege","summary":"A memory leak in Linux kernel histogram triggers allows local attackers to exhaust memory by removing triggers with multiple variable references.","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 var refs regardless of how often they are referenced\n\nUsing the same variable three or more times in one hist trigger leaks the\nvariable reference and its strings when the trigger is removed.\n\ncommit 656fe2ba85e8 (\"tracing: Use hist trigger's var_ref array to destroy\nvar_refs\") made a trigger's var_refs[] array the only owner of a var ref:\ndestroy_hist_field() returns early for HIST_FIELD_FL_VAR_REF, so the field\nexpressions never destroy one. One entry, freed once, no count needed.\n\ncommit 8bcebc77e85f (\"tracing: Fix histogram code when expression has same\nvar as value\") then made repeated references share one object and added a\ncount of them. Only the increment side exists, since those expressions\nstill return early and never drop a reference, so __destroy_hist_field()\nsees how many references were created rather than how many are left. It\nfrees when the decremented count is 0 or 1, so two references work and\nthree or more leak.\n\nSharing kept one array entry per object, and create_var_ref() searches and\nappends within a single trigger, so nothing outside it holds the object.\nRemoving a trigger whose variables are still referenced is already refused\nby check_var_refs() with -EBUSY. Drop the count and free unconditionally.","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 var refs regardless of how often they are referenced","id":"CVE-2026-97922","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 the var ref when its initialization fails","id":"CVE-2026-97923"},"packages":[],"prev":{"headline":"tracing: Free histogram the field rejected for a bad modifier","id":"CVE-2026-97921"},"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 Linux kernel histogram triggers allows local attackers to exhaust memory by removing triggers with multiple variable references.","url":"https://insights.sbomify.com/CVE-2026-97922/"}