UBUNTU-CVE-2026-98044: Medium severity ubuntu/linux-hwe-edge vulnerability
In the Linux kernel, the following vulnerability has been resolved: bpf: Reject legacy packet loads from callbacks checkldabs() models a failed BPFLDABS or BPFLDIND in a subprogram as an implicit return with R0 set to zero. It calls preparefuncexit() to explore this synthesized path. When the load is reached directly from a synchronous callback, preparefuncexit() enforces the callback return contract and marks R0 precise. R0 is not derived from a real instruction on this path, so precision backtracking reaches the callback call with R0 still requested and triggers the "callback unexpected regs" verifier bug. A privileged program loader can therefore cause a verifier warning and an -EFAULT BPFPROGLOAD. These legacy packet-load instructions are deprecated. Reject them from callbacks rather than complicating their implicit-return model. Check all active frames before constructing the implicit return so nested static subprograms cannot hide the callback context. Global functions are verified independently with a fresh frame zero, so an active-frame check cannot identify a global function called from a callback. Also check the complete subprogram call graph during stack-depth validation and reject a function containing a legacy load when any caller is a callback. This covers global and static descendants without making hasldabs transitive, preserving its per-function BTF return-type check. Ordinary uses outside callbacks remain supported.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1 - Compensating control
Reject legacy BPF_LD_ABS and BPF_LD_IND packet loads from callbacks; ordinary uses outside callbacks remain supported.
Event History
Frequently Asked Questions
Who can trigger this issue?
A privileged BPF program loader can trigger it. The affected program uses deprecated BPF_LD_ABS or BPF_LD_IND packet-load instructions from a callback context, including callback contexts hidden through nested static subprograms or the relevant subprogram call graph.
What is the observable impact of an attempted exploit?
The BPF verifier can emit a "callback unexpected regs" warning and reject the program load with -EFAULT BPF_PROG_LOAD. The stated impact is limited to availability; confidentiality and integrity impacts are not indicated.
Are legacy packet-load instructions still supported in callback code?
They are deprecated, and the resolution is to reject legacy packet loads from callbacks. Programs relying on these instructions in callback-reachable code should be revised to avoid them.