UBUNTU-CVE-2023-53421
In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats() When blkg_alloc() is called to allocate a blkcg_gq structure with the associated blkg_iostat_set's, there are 2 fields within blkg_iostat_set that requires proper initialization - blkg & sync. The former field was introduced by commit 3b8cc6298724 ("blk-cgroup: Optimize blkcg_rstat_flush()") while the later one was introduced by commit f73316482977 ("blk-cgroup: reimplement basic IO stats using cgroup rstat"). Unfortunately those fields in the blkg_iostat_set's are not properly re-initialized when they are cleared in v1's blkcg_reset_stats(). This can lead to a kernel panic due to NULL pointer access of the blkg pointer. The missing initialization of sync is less problematic and can be a problem in a debug kernel due to missing lockdep initialization. Fix these problems by re-initializing them after memory clearing.
02 / AFFECTED SOFTWARE
Affected packages
16 explicit affected versions
83 explicit affected versions
12 explicit affected versions
7 explicit affected versions
11 explicit affected versions
82 explicit affected versions
12 explicit affected versions
69 explicit affected versions
85 explicit affected versions
3 explicit affected versions
7 explicit affected versions
2 explicit affected versions
51 explicit affected versions
50 explicit affected versions
6 explicit affected versions
12 explicit affected versions
19 explicit affected versions
6 explicit affected versions
92 explicit affected versions
24 explicit affected versions
77 explicit affected versions
77 explicit affected versions
80 explicit affected versions
72 explicit affected versions
10 explicit affected versions
26 explicit affected versions
84 explicit affected versions
7 explicit affected versions
79 explicit affected versions
13 explicit affected versions
35 explicit affected versions
44 explicit affected versions
42 explicit affected versions
18 explicit affected versions
36 explicit affected versions
64 explicit affected versions
13 explicit affected versions
4 explicit affected versions
23 explicit affected versions
1 explicit affected versions
21 explicit affected versions
16 explicit affected versions
10 explicit affected versions
8 explicit affected versions
7 explicit affected versions
12 explicit affected versions
7 explicit affected versions
12 explicit affected versions
14 explicit affected versions
1 explicit affected versions
7 explicit affected versions
12 explicit affected versions
12 explicit affected versions
38 explicit affected versions
10 explicit affected versions
37 explicit affected versions
13 explicit affected versions
10 explicit affected versions
59 explicit affected versions
26 explicit affected versions
13 explicit affected versions
32 explicit affected versions
29 explicit affected versions
13 explicit affected versions
89 explicit affected versions
84 explicit affected versions
47 explicit affected versions
33 explicit affected versions
23 explicit affected versions
53 explicit affected versions
10 explicit affected versions
10 explicit affected versions
26 explicit affected versions
1 explicit affected versions
61 explicit affected versions
11 explicit affected versions
13 explicit affected versions
74 explicit affected versions
1 explicit affected versions
1 explicit affected versions
1 explicit affected versions
83 explicit affected versions
73 explicit affected versions
73 explicit affected versions
13 explicit affected versions
43 explicit affected versions
10 explicit affected versions
8 explicit affected versions
14 explicit affected versions
4 explicit affected versions
78 explicit affected versions
11 explicit affected versions
1 explicit affected versions
73 explicit affected versions
18 explicit affected versions
12 explicit affected versions
66 explicit affected versions
72 explicit affected versions
27 explicit affected versions
58 explicit affected versions
8 explicit affected versions
49 explicit affected versions
5 explicit affected versions
3 explicit affected versions
8 explicit affected versions
10 explicit affected versions
7 explicit affected versions
13 explicit affected versions
13 explicit affected versions
7 explicit affected versions
10 explicit affected versions
12 explicit affected versions
31 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
14 explicit affected versions
38 explicit affected versions
9 explicit affected versions
11 explicit affected versions
85 explicit affected versions
7 explicit affected versions
4 explicit affected versions
03 / CONNECTIONS
Connected vulnerabilities
04 / EVIDENCE
Source records
In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats() When blkg_alloc() is called to allocate a blkcg_gq structure with the associated blkg_iostat_set's, there are 2 fields within blkg_iostat_set that requires proper initialization - blkg & sync. The former field was introduced by commit 3b8cc6298724 ("blk-cgroup: Optimize blkcg_rstat_flush()") while the later one was introduced by commit f73316482977 ("blk-cgroup: reimplement basic IO stats using cgroup rstat"). Unfortunately those fields in the blkg_iostat_set's are not properly re-initialized when they are cleared in v1's blkcg_reset_stats(). This can lead to a kernel panic due to NULL pointer access of the blkg pointer. The missing initialization of sync is less problematic and can be a problem in a debug kernel due to missing lockdep initialization. Fix these problems by re-initializing them after memory clearing.
05 / REFERENCES
Further evidence
- https://git.kernel.org/linus/3d2af77e31ade05ff7ccc3658c3635ec1bea0979
- https://git.kernel.org/stable/c/3d2af77e31ade05ff7ccc3658c3635ec1bea0979
- https://git.kernel.org/stable/c/abbce7f82613ea5eeefd0fc3c1c8e449b9cef2a2
- https://git.kernel.org/stable/c/b0d26283af612b9e0cc3188b0b88ad7fdea447e8
- https://ubuntu.com/security/CVE-2023-53421
- https://ubuntu.com/security/notices/USN-8162-1
- https://ubuntu.com/security/notices/USN-8180-1
- https://ubuntu.com/security/notices/USN-8180-2
- https://ubuntu.com/security/notices/USN-8180-3
- https://ubuntu.com/security/notices/USN-8180-4
- https://ubuntu.com/security/notices/USN-8180-5
- https://ubuntu.com/security/notices/USN-8180-6
- https://ubuntu.com/security/notices/USN-8186-1
- https://ubuntu.com/security/notices/USN-8187-1
- https://ubuntu.com/security/notices/USN-8188-1
- https://ubuntu.com/security/notices/USN-8243-1
- https://ubuntu.com/security/notices/USN-8275-1
- https://ubuntu.com/security/notices/USN-8297-1
- https://www.cve.org/CVERecord?id=CVE-2023-53421