CVE-2026-97944x86/cfi: Fix FineIBT hash offset in cfi_get_func_hash()
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Sep 25, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 85a2d4a890dce3cfc9c14aa91afc3dd7af8e3bf5 before cd9b4595d6283f9b8a35d7ae607508de45a351ce; 85a2d4a890dce3cfc9c14aa91afc3dd7af8e3bf5 builds before 67cf94c30a8b5ebc839f282f5c5a522b35903524; 85a2d4a890dce3cfc9c14aa91afc3dd7af8e3bf5 builds before 5a5d26f2cfe13467166219f6bf58099326912ddb | CNA record |
References
- https://git.kernel.org/stable/c/cd9b4595d6283f9b8a35d7ae607508de45a351ce
- https://git.kernel.org/stable/c/67cf94c30a8b5ebc839f282f5c5a522b35903524
- https://git.kernel.org/stable/c/5a5d26f2cfe13467166219f6bf58099326912ddb
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.