CVE-2026-98061
N/A
Summary
In the Linux kernel, the following vulnerability has been resolved:
bpf: Reject tail calls directly from callback frames
A tail call from a non-zero frame is modeled as a return from that frame. The verifier makes R0 unknown and calls prepare_func_exit() for the taken branch.
When the current frame is a synchronous callback, prepare_func_exit() enforces the callback return-value contract and marks R0 precise. Since the tail-call path synthesized R0 rather than deriving it from an instruction, precision backtracking reaches the callback-calling instruction with R0 still requested and triggers the "callback unexpected regs" verifier bug. A CAP_BPF task can therefore cause a WARN and an -EFAULT BPF_PROG_LOAD.
Tail calls reachable from callbacks are already rejected later by check_max_stack_depth(). Reject a tail call made directly by a callback before constructing the inconsistent return state, using the existing diagnostic. Tail calls from ordinary subprograms keep their current behavior.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Linux | Linux | a6c22c91b6284e4713c0cf5b20ab3c9c71b77ae8 < 617c8266e49f45747f71e74177646a63f72b7025 | affected |
| Linux | Linux | e3245f8990431950d20631c72236d4e8cb2dcde8 < 96d31b28263c429a56e4de85bcf744a5c320b3a3 | affected |
| Linux | Linux | e3245f8990431950d20631c72236d4e8cb2dcde8 < 266aa4ad0b2e82397cd9045752c9bff03d98eddd | affected |
| Linux | Linux | 6.18.2 < 6.18.53 | affected |
| Linux | Linux | 6.19 | affected |
| Linux | Linux | 0 < 6.19 | unaffected |
| Linux | Linux | 6.18.53 <= 6.18.* | unaffected |
| Linux | Linux | 7.2.7 <= 7.2.* | unaffected |
| Linux | Linux | 7.3-rc2 <= * | unaffected |
Weaknesses
References
- https://git.kernel.org/stable/c/617c8266e49f45747f71e74177646a63f72b7025
- https://git.kernel.org/stable/c/96d31b28263c429a56e4de85bcf744a5c320b3a3
- https://git.kernel.org/stable/c/266aa4ad0b2e82397cd9045752c9bff03d98eddd
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.