bpf: Fix missing migration protection in __rhtab_map_lookup_and_delete_batch()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix missing migration protection in __rhtab_map_lookup_and_delete_batch()
bpf_mem_cache_free_rcu() uses this_cpu_ptr() which requires migration to be disabled. All callers of rhtab_delete_elem() disable migration except __rhtab_map_lookup_and_delete_batch(), which calls it under rcu_read_lock() only.
On CONFIG_PREEMPT_RCU, rcu_read_lock() does not disable preemption or migration, so the task can migrate between CPUs during the delete loop, causing this_cpu_ptr() to trigger:
BUG: using smp_processor_id() in preemptible [00000000] code
Fix by wrapping the delete loop in migrate_disable()/migrate_enable() in __rhtab_map_lookup_and_delete_batch(), matching the migration protection that the other callers already provide.
From the CVE record · Linux
The Linux kernel’s BPF hash-table batch deletion path lacks migration protection. On kernels built with CONFIG_PREEMPT_RCU, a task that migrates between CPUs during the delete loop can trigger a kernel BUG; the input does not specify whether an attacker can trigger this or what access is required.
Engineers running Linux kernels with CONFIG_PREEMPT_RCU should check whether their kernel includes the fix; affected versions are not specified.