CVE-2024-38384
Medium
Elevated severity or exploit probability.
CVSS base
7.8
HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS — probability of exploitation (30 days)
0.2%
14.8th percentile
CISA KEV
Not listed
Weakness / dates
CWE-400
Published 2024-06-24 · modified 2026-08-04
CVSS breakdown
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
| Attack Vector | L | Local |
| Attack Complexity | L | Low |
| Privileges Required | L | Low |
| User Interaction | N | None |
| Scope | U | Unchanged |
| Confidentiality | H | High |
| Integrity | H | High |
| Availability | H | High |
Timeline
- 2024-06-24 — Published (NVD)
- 2026-08-04 — Last modified (NVD)
Description
In 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.
Affected
References
- https://git.kernel.org/stable/c/714e59b5456e4d6e4295a9968c564abe193f461c
- https://git.kernel.org/stable/c/785298ab6b802afa75089239266b6bbea590809c
- https://git.kernel.org/stable/c/d0aac2363549e12cc79b8e285f13d5a9f42fd08e
- https://git.kernel.org/stable/c/714e59b5456e4d6e4295a9968c564abe193f461c
- https://git.kernel.org/stable/c/785298ab6b802afa75089239266b6bbea590809c
- https://git.kernel.org/stable/c/d0aac2363549e12cc79b8e285f13d5a9f42fd08e