{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97944 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97944 is a denial of service 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-97944 and fix it if it is affected.\n\nWhat it is: CVE-2026-97944 is a denial of service 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-97944 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-97944/ (Markdown: https://insights.sbomify.com/CVE-2026-97944/index.md)","id":"CVE-2026-97944","markdown":"https://insights.sbomify.com/CVE-2026-97944/index.md","name":"CVE-2026-97944","record":{"aliases":["BELL-CVE-2026-97944","DEBIAN-CVE-2026-97944","GHSA-7jp9-pjx7-g496","UBUNTU-CVE-2026-97944"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"no","non_default_config":true,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A kernel bug causes a crash when BPF struct_ops programs are used with FineIBT enabled, requiring local access to trigger.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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\nx86/cfi: Fix FineIBT hash offset in cfi_get_func_hash()\n\nThe switch of the FineIBT preamble from \"subl $hash, %r10d\" to the\nshorter \"subl $hash, %eax\" moved the hash immediate from offset 7 to\noffset 5 of the preamble. fineibt_preamble_hash was updated to match,\nbut the open-coded offset in cfi_get_func_hash() was missed and it\nstill reads the hash at offset 7.\n\ncfi_get_func_hash() is used by the BPF JIT to give a struct_ops\ntrampoline the CFI hash of the stub function it stands in for. With\nFineIBT the trampoline now gets the upper half of the real hash\nfollowed by the first two bytes of the next instruction, so the first\nindirect call from the kernel into a struct_ops program,\ntcp_init_congestion_control() calling -\u003einit() of a BPF congestion\ncontrol for example, fails the FineIBT check and the kernel dies with\na CFI failure.\n\nMove the FineIBT preamble template and its offset defines above\ncfi_get_func_hash() and use fineibt_preamble_hash there, so every\nreader of the preamble shares one definition of its layout. The\nCFI_FINEIBT arm is only built with CONFIG_FINEIBT, the only\nconfiguration in which cfi_mode can take that value.\ncfi_get_func_arity() does not need the same treatment: the __bhi_args\ncall whose displacement it reads still ends at the function address.","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":"x86/cfi: Fix FineIBT hash offset in cfi_get_func_hash()","id":"CVE-2026-97944","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"x86/mm: Fix user-space data loss with MADV_FREE and THP","id":"CVE-2026-97945"},"packages":[],"prev":{"headline":"x86/mm/pat: Acquire init_mm write lock on collapse to avoid UAF","id":"CVE-2026-97943"},"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 kernel bug causes a crash when BPF struct_ops programs are used with FineIBT enabled, requiring local access to trigger.","url":"https://insights.sbomify.com/CVE-2026-97944/"}