bpf: Fix vmlinux BTF prep race in bpf_get_btf_vmlinux
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 8580ac9404f6240668a026785d7d8856f0530409 · < 2892f3f44bf865c8fb6b6c0960edec4cc91806ee| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix vmlinux BTF prep race in bpf_get_btf_vmlinux
bpf_get_btf_vmlinux() lazily parses the vmlinux BTF under the bpf_verifier_lock, but publishes the result through a plain store and re-checks it through a plain lockless load. Nothing orders the stores initializing the struct btf inside btf_parse_vmlinux() against the store publishing the pointer: On a weakly ordered arch, a concurrent first-time caller taking the lockless fast path could in principle observe the pointer before the parsed contents are visible. The mutex_unlock() does not help such a reader given it only synchronizes with a later acquisition of the same lock. Thus, publish the pointer with smp_store_release() and read it on the fast path with smp_load_acquire().
Acquire semantics are needed rather than a dependency-ordered READ_ONCE(): btf_parse_vmlinux() also populates globals outside the returned object (e.g. bpf_ctx_convert.t). An address dependency would only order accesses performed through the pointer and not cover other globals.
From the CVE record · Linux
The Linux kernel can publish parsed vmlinux BTF data before its initialization is visible to another CPU. On a weakly ordered architecture, a concurrent first-time caller could observe incompletely initialized data. The input does not specify an attacker capability, authentication requirement, or user interaction.
Engineers running Linux kernels should check whether their versions are affected; no version range is provided.