All vulnerabilities
CVE-2026-97944

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

Linux LinuxOperating systems
CVSS
NoneNot scored
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.17%Chance of exploitation activity in the next 30 days, higher than 5% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in67cf94c30a8b5ebc839f282f5c5a522b35903524Also 5a5d26f2cfe13467166219f6bf58099326912ddbCVE List
Published25 Sep 2026Updated 19 Oct 2026CVE List

What fixes it

  • 67cf94c30a8b5ebc839f282f5c5a522b35903524LinuxCVE List
  • 5a5d26f2cfe13467166219f6bf58099326912ddbLinuxCVE List

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

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.

Text from CVE List

Affected versions 8

  • Linuxaffected: 85a2d4a890dce3cfc9c14aa91afc3dd7af8e3bf5 before cd9b4595d6283f9b8a35d7ae607508de45a351ceCVE List
  • Linuxaffected: 85a2d4a890dce3cfc9c14aa91afc3dd7af8e3bf5 before 67cf94c30a8b5ebc839f282f5c5a522b35903524CVE List
  • Linuxaffected: 85a2d4a890dce3cfc9c14aa91afc3dd7af8e3bf5 before 5a5d26f2cfe13467166219f6bf58099326912ddbCVE List
  • Linuxaffected: 6.18CVE List
  • Linuxunaffected: all versions before 6.18CVE List
  • Linuxunaffected: 6.18.53 through 6.18.*CVE List
  • Linuxunaffected: 7.2.7 through 7.2.*CVE List
  • Linuxunaffected: 7.3CVE List

References 3