UBUNTU-CVE-2025-21853
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/[email protected]/
02 / AFFECTED SOFTWARE
Affected packages
11 explicit affected versions
67 explicit affected versions
50 explicit affected versions
6 explicit affected versions
12 explicit affected versions
19 explicit affected versions
6 explicit affected versions
77 explicit affected versions
24 explicit affected versions
62 explicit affected versions
62 explicit affected versions
70 explicit affected versions
57 explicit affected versions
10 explicit affected versions
19 explicit affected versions
26 explicit affected versions
69 explicit affected versions
7 explicit affected versions
67 explicit affected versions
23 explicit affected versions
13 explicit affected versions
25 explicit affected versions
35 explicit affected versions
29 explicit affected versions
27 explicit affected versions
18 explicit affected versions
27 explicit affected versions
64 explicit affected versions
28 explicit affected versions
13 explicit affected versions
4 explicit affected versions
23 explicit affected versions
33 explicit affected versions
1 explicit affected versions
21 explicit affected versions
16 explicit affected versions
10 explicit affected versions
29 explicit affected versions
5 explicit affected versions
7 explicit affected versions
12 explicit affected versions
4 explicit affected versions
12 explicit affected versions
14 explicit affected versions
1 explicit affected versions
7 explicit affected versions
3 explicit affected versions
12 explicit affected versions
12 explicit affected versions
23 explicit affected versions
23 explicit affected versions
18 explicit affected versions
15 explicit affected versions
10 explicit affected versions
37 explicit affected versions
5 explicit affected versions
13 explicit affected versions
21 explicit affected versions
10 explicit affected versions
44 explicit affected versions
26 explicit affected versions
13 explicit affected versions
16 explicit affected versions
29 explicit affected versions
13 explicit affected versions
74 explicit affected versions
22 explicit affected versions
23 explicit affected versions
69 explicit affected versions
32 explicit affected versions
33 explicit affected versions
23 explicit affected versions
38 explicit affected versions
10 explicit affected versions
1 explicit affected versions
11 explicit affected versions
12 explicit affected versions
7 explicit affected versions
12 explicit affected versions
54 explicit affected versions
70 explicit affected versions
10 explicit affected versions
26 explicit affected versions
25 explicit affected versions
1 explicit affected versions
46 explicit affected versions
16 explicit affected versions
28 explicit affected versions
13 explicit affected versions
28 explicit affected versions
16 explicit affected versions
71 explicit affected versions
31 explicit affected versions
3 explicit affected versions
4 explicit affected versions
2 explicit affected versions
51 explicit affected versions
13 explicit affected versions
24 explicit affected versions
12 explicit affected versions
59 explicit affected versions
57 explicit affected versions
27 explicit affected versions
44 explicit affected versions
24 explicit affected versions
8 explicit affected versions
34 explicit affected versions
5 explicit affected versions
3 explicit affected versions
8 explicit affected versions
10 explicit affected versions
4 explicit affected versions
27 explicit affected versions
13 explicit affected versions
13 explicit affected versions
7 explicit affected versions
3 explicit affected versions
10 explicit affected versions
12 explicit affected versions
17 explicit affected versions
44 explicit affected versions
16 explicit affected versions
3 explicit affected versions
13 explicit affected versions
26 explicit affected versions
45 explicit affected versions
37 explicit affected versions
32 explicit affected versions
14 explicit affected versions
38 explicit affected versions
9 explicit affected versions
11 explicit affected versions
21 explicit affected versions
7 explicit affected versions
70 explicit affected versions
7 explicit affected versions
4 explicit affected versions
59 explicit affected versions
1 explicit affected versions
1 explicit affected versions
1 explicit affected versions
68 explicit affected versions
58 explicit affected versions
58 explicit affected versions
13 explicit affected versions
43 explicit affected versions
10 explicit affected versions
8 explicit affected versions
26 explicit affected versions
14 explicit affected versions
4 explicit affected versions
78 explicit affected versions
11 explicit affected versions
1 explicit affected versions
21 explicit affected versions
59 explicit affected versions
03 / CONNECTIONS
Connected vulnerabilities
04 / EVIDENCE
Source records
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/[email protected]/
05 / REFERENCES
Further evidence
- https://git.kernel.org/linus/bc27c52eea189e8f7492d40739b7746d67b65beb
- https://git.kernel.org/stable/c/271e49f8a58edba65bc2b1250a0abaa98c4bfdbe
- https://git.kernel.org/stable/c/29cfda62ab4d92ab94123813db49ab76c1e61b29
- https://git.kernel.org/stable/c/bc27c52eea189e8f7492d40739b7746d67b65beb
- https://git.kernel.org/stable/c/d95607a5f2f9bb08194c9deaf4a5f3e8ba59a9d4
- https://ubuntu.com/security/CVE-2025-21853
- https://ubuntu.com/security/notices/USN-7521-1
- https://ubuntu.com/security/notices/USN-7521-2
- https://ubuntu.com/security/notices/USN-7521-3
- https://ubuntu.com/security/notices/USN-7654-1
- https://ubuntu.com/security/notices/USN-7654-2
- https://ubuntu.com/security/notices/USN-7654-3
- https://ubuntu.com/security/notices/USN-7654-4
- https://ubuntu.com/security/notices/USN-7654-5
- https://ubuntu.com/security/notices/USN-7655-1
- https://ubuntu.com/security/notices/USN-7686-1
- https://ubuntu.com/security/notices/USN-7703-1
- https://ubuntu.com/security/notices/USN-7703-2
- https://ubuntu.com/security/notices/USN-7703-3
- https://ubuntu.com/security/notices/USN-7703-4
- https://ubuntu.com/security/notices/USN-7711-1
- https://ubuntu.com/security/notices/USN-7712-1
- https://ubuntu.com/security/notices/USN-7712-2
- https://ubuntu.com/security/notices/USN-7719-1
- https://ubuntu.com/security/notices/USN-7737-1
- https://www.cve.org/CVERecord?id=CVE-2025-21853