bpf: Fix mmap_lock leak in irq_work path
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ eac9153f2b584c702cea02c1f1a57d85aa9aea42 · < fa9dcacdcdf487f0ffef64bf67622f1caed509f1| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix mmap_lock leak in irq_work path
stack_map_get_build_id_offset() introduced a per-CPU irq_work to defer mmap_read_unlock() from NMI context, and bpf_find_vma() later reused the same mmap_unlock_work. Both callers only check whether the work is busy before taking mmap_lock, so a nested caller can reuse the slot before the first caller queues it. Two read locks may then be acquired while only one deferred unlock runs, leaking a read lock and blocking exit_mmap().
Reserve the per-CPU slot before mmap_read_trylock(). Use the same wrapper in stackmap and bpf_find_vma() so both callers release the reservation on trylock failure. Keep rejecting the slot while the irq_work remains busy. Release it after the irq_work callback unlocks the mm.
From the CVE record · Linux
A per-CPU irq_work slot can be reused by nested BPF callers before the first caller queues it, causing two mmap read locks to be acquired but only one to be released. The leaked lock can block exit_mmap(). The input does not specify an attack route, authentication requirement, or user interaction.
Engineers running the Linux kernel should check their builds; affected versions are not specified.