Description
In the Linux kernel, the following vulnerability has been resolved: bpf: crypto: Use the correct destructor kfunc type With CONFIG_CFI enabled, the kernel strictly enforces that indirect function calls use a function pointer type that matches the target function. I ran into the following type mismatch when running BPF self-tests: CFI failure at bpf_obj_free_fields+0x190/0x238 (target: bpf_crypto_ctx_release+0x0/0x94; expected type: 0xa488ebfc) Internal error: Oops - CFI: 00000000f2008228 [#1] SMP ... As bpf_crypto_ctx_release() is also used in BPF programs and using a void pointer as the argument would make the verifier unhappy, add a simple stub function with the correct type and register it as the destructor kfunc instead.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
3e1c6f35409f9e447bf37f64840f5b65576bfb78 to < 4e3e57dbf46dad3498f8c4219ce2dba756875962affected3e1c6f35409f9e447bf37f64840f5b65576bfb78 to < 50d6fd69388cc7b05dce72f09080674dcede4ac9affected3e1c6f35409f9e447bf37f64840f5b65576bfb78 to < 3979a550fe06b370d73647f59cf462fa525c9ec4affected3e1c6f35409f9e447bf37f64840f5b65576bfb78 to < b40a5d724f29fc2eed23ff353808a9aae616b48aaffected
Linux Linux
Default version status: affected
6.10affected0 to < 6.10unaffected6.12.75 to ≤ 6.12.*unaffected6.18.16 to ≤ 6.18.*unaffected6.19.6 to ≤ 6.19.*unaffected7.0 to ≤ *unaffected