bpf: avoid holding freeze_mutex during mmap operation
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ fc9702273e2edb90400a34b3be76f7b08fa3344b · < 271e49f8a58edba65bc2b1250a0abaa98c4bfdbe| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bpf: avoid holding freeze_mutex during mmap operation
We use map->freeze_mutex to prevent races between map_freeze() and memory mapping BPF map contents with writable permissions. The way we naively do this means we'll hold freeze_mutex for entire duration of all the mm and VMA manipulations, which is completely unnecessary. This can potentially also lead to deadlocks, as reported by syzbot in [0].
So, instead, hold freeze_mutex only during writeability checks, bump (proactively) "write active" count for the map, unlock the mutex and proceed with mmap logic. And only if something went wrong during mmap logic, then undo that "write active" counter increment.
[0] https://lore.kernel.org/bpf/678dcbc9.050a0220.303755.0066.GAE@google.com/
From the CVE record · Linux
The Linux kernel can hold a BPF map's freeze_mutex throughout memory mapping operations. This can potentially cause a deadlock when mapping BPF map contents with writable permissions. The input does not specify access or authentication requirements.
Teams running Linux kernels with the affected BPF map mmap behavior should check their versions; affected versions are not specified.