Answer in brief
CVE-2024-38384 records a Unknown severity vulnerability in blk-cgroup: fix list corruption from reorder of WRITE ->lqueued. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic), linux/linux_kernel (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic), linux/linux_kernel (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3b8cc6298724021da845f2f9fd7dd4b6829a6817 <714e59b5456e4d6e4295a9968c564abe193f461c || >=3b8cc6298724021da845f2f9fd7dd4b6829a6817 <785298ab6b802afa75089239266b6bbea590809c || >=3b8cc6298724021da845f2f9fd7dd4b6829a6817 <d0aac2363549e12cc79b8e285f13d5a9f42fd08e | 714e59b5456e4d6e4295a9968c564abe193f461c, 785298ab6b802afa75089239266b6bbea590809c, d0aac2363549e12cc79b8e285f13d5a9f42fd08e |
| Linux/Linuxgeneric | 6.2 | Not reported |
| linux/linux_kernelgeneric | >=3b8cc6298724 <714e59b5456e | 714e59b5456e |
| linux/linux_kernelgeneric | >=3b8cc6298724 <785298ab6b80 | 785298ab6b80 |
| linux/linux_kernelgeneric | >=3b8cc6298724 <d0aac2363549 | d0aac2363549 |
| linux/linux_kernelgeneric | 6.2 | Not reported |
Published upstream
Jun 24, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-38384 records a Unknown severity vulnerability in blk-cgroup: fix list corruption from reorder of WRITE ->lqueued. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic), linux/linux_kernel (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic), linux/linux_kernel (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3b8cc6298724021da845f2f9fd7dd4b6829a6817 <714e59b5456e4d6e4295a9968c564abe193f461c || >=3b8cc6298724021da845f2f9fd7dd4b6829a6817 <785298ab6b802afa75089239266b6bbea590809c || >=3b8cc6298724021da845f2f9fd7dd4b6829a6817 <d0aac2363549e12cc79b8e285f13d5a9f42fd08e | 714e59b5456e4d6e4295a9968c564abe193f461c, 785298ab6b802afa75089239266b6bbea590809c, d0aac2363549e12cc79b8e285f13d5a9f42fd08e |
| Linux/Linuxgeneric | 6.2 | Not reported |
| linux/linux_kernelgeneric | >=3b8cc6298724 <714e59b5456e | 714e59b5456e |
| linux/linux_kernelgeneric | >=3b8cc6298724 <785298ab6b80 | 785298ab6b80 |
| linux/linux_kernelgeneric | >=3b8cc6298724 <d0aac2363549 | d0aac2363549 |
| linux/linux_kernelgeneric | 6.2 | Not reported |
Published upstream
Jun 24, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.