CVE-2026-97944

x86/cfi: Fix FineIBT hash offset in cfi_get_func_hash()

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.

Key facts

Published
25 Sep 2026
Last changed
19 Oct 2026
Assigned by
Linux
EPSS
0.166% likely to be exploited in the next 30 days, higher than 5.896% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 85a2d4a890dce3cfc9c14aa91afc3dd7af8e3bf5 up to but excluding cd9b4595d6283f9b8a35d7ae607508de45a351ce (affected)
  • 85a2d4a890dce3cfc9c14aa91afc3dd7af8e3bf5 up to but excluding 67cf94c30a8b5ebc839f282f5c5a522b35903524 (affected)
  • 85a2d4a890dce3cfc9c14aa91afc3dd7af8e3bf5 up to but excluding 5a5d26f2cfe13467166219f6bf58099326912ddb (affected)
LinuxLinux
  • Default status: affected
  • 6.18 (affected)
  • 0 up to but excluding 6.18 (unaffected)
  • 6.18.53 up to and including 6.18.* (unaffected)
  • 7.2.7 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 25 Sep 2026 Published

References