blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f73316482977ac401ac37245c9df48079d4e11f3 · < 3d2af77e31ade05ff7ccc3658c3635ec1bea0979| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's blk-cgroup code fails to reinitialize fields after v1 I/O statistics are reset. A NULL pointer access can cause a kernel panic; the input does not specify an attack path or authentication requirements.
Engineers running Linux kernels that use blk-cgroup v1 should check whether their kernel includes the fix; affected versions were not provided.