CVE-2024-50063
- Source
- https://nvd.nist.gov/vuln/detail/CVE-2024-50063
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2024-50063.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2024-50063
- Downstream
- Related
- Published
- 2024-10-21T19:39:51Z
- Modified
- 2025-10-17T16:13:03.599043Z
- Summary
- bpf: Prevent tail call between progs attached to different hooks
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
bpf: Prevent tail call between progs attached to different hooks
bpf progs can be attached to kernel functions, and the attached functions can take different parameters or return different return values. If prog attached to one kernel function tail calls prog attached to another kernel function, the ctx access or return value verification could be bypassed.
For example, if prog1 is attached to func1 which takes only 1 parameter and prog2 is attached to func2 which takes two parameters. Since verifier assumes the bpf ctx passed to prog2 is constructed based on func2's prototype, verifier allows prog2 to access the second parameter from the bpf ctx passed to it. The problem is that verifier does not prevent prog1 from passing its bpf ctx to prog2 via tail call. In this case, the bpf ctx passed to prog2 is constructed from func1 instead of func2, that is, the assumption for ctx access verification is bypassed.
Another example, if BPF LSM prog1 is attached to hook fileallocsecurity, and BPF LSM prog2 is attached to hook bpflsmauditruleknown. Verifier knows the return value rules for these two hooks, e.g. it is legal for bpflsmauditruleknown to return positive number 1, and it is illegal for fileallocsecurity to return positive number. So verifier allows prog2 to return positive number 1, but does not allow prog1 to return positive number. The problem is that verifier does not prevent prog1 from calling prog2 via tail call. In this case, prog2's return value 1 will be used as the return value for prog1's hook fileallocsecurity. That is, the return value rule is bypassed.
This patch adds restriction for tail call to prevent such bypasses.
- References
-
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- https://git.kernel.org/stable/c/28ead3eaabc16ecc907cfb71876da028080f6356
- https://git.kernel.org/stable/c/5d5e3b4cbe8ee16b7bf96fd73a421c92a9da3ca1
- https://git.kernel.org/stable/c/88c2a10e6c176c2860cd0659f4c0e9d20b3f64d1
- https://git.kernel.org/stable/c/d9a807fb7cbfad4328824186e2e4bee28f72169b
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introducedf1b9509c2fb0ef4db8d22dac9aef8e856a5d81f6Fixedd9a807fb7cbfad4328824186e2e4bee28f72169b
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introducedf1b9509c2fb0ef4db8d22dac9aef8e856a5d81f6Fixed5d5e3b4cbe8ee16b7bf96fd73a421c92a9da3ca1
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introducedf1b9509c2fb0ef4db8d22dac9aef8e856a5d81f6Fixed88c2a10e6c176c2860cd0659f4c0e9d20b3f64d1
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introducedf1b9509c2fb0ef4db8d22dac9aef8e856a5d81f6Fixed28ead3eaabc16ecc907cfb71876da028080f6356