blk-cgroup: fix list corruption from reorder of WRITE ->lqueued
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.6.336.9.46.10In the Linux kernel, the following vulnerability has been resolved:
blk-cgroup: fix list corruption from reorder of WRITE ->lqueued
__blkcg_rstat_flush() can be run anytime, especially when blk_cgroup_bio_start is being executed.
If WRITE of `->lqueued` is re-ordered with READ of 'bisc->lnode.next' in the loop of __blkcg_rstat_flush(), `next_bisc` can be assigned with one stat instance being added in blk_cgroup_bio_start(), then the local list in __blkcg_rstat_flush() could be corrupted.
Fix the issue by adding one barrier.
From the CVE record · Linux
A memory-ordering issue in the Linux kernel’s blk-cgroup code can corrupt a local statistics list when a statistics flush overlaps with bio accounting. The input does not specify how an attacker could trigger this, or whether network access, authentication, or user interaction is required.
Engineers running the Linux kernel should check their kernel versions; affected versions are not specified in the input.