Answer in brief
CVE-2023-52983 records a High severity (CVSS 7.8) vulnerability in block, bfq: fix uaf for bfqq in bic_set_bfqq(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5533742c7cb1bc9b1f0bf401cc397d44a3a9e07a <7f77f3dab5066a7c9da73d72d1eee895ff84a8d5 || >=094f3d9314d67691cb21ba091c1b528f6e3c4893 <511c922c5bf6c8a166bea826e702336bc2424140 || >=761564d93c8265f65543acf0a576b32d66bfa26a <cb1876fc33af26d00efdd473311f1b664c77c44e || >=64dc8c732f5c2b406cc752e6aaa1bd5471159cab <b600de2d7d3a16f9007fad1bdae82a3951a26af2 || b22fd72bfebda3956efc4431b60ddfc0a51e03e0 || >=6.0.16 <6.1 | 7f77f3dab5066a7c9da73d72d1eee895ff84a8d5, 511c922c5bf6c8a166bea826e702336bc2424140, cb1876fc33af26d00efdd473311f1b664c77c44e, b600de2d7d3a16f9007fad1bdae82a3951a26af2, 6.1 |
| Linux/Linuxgeneric | >=5.15.86 <5.15.93 || >=6.1.2 <6.1.11 | 5.15.93, 6.1.11 |
Published upstream
Mar 27, 2025
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: block, bfq: fix uaf for bfqq in bic_set_bfqq() After commit 64dc8c732f5c ("block, bfq: fix possible uaf for 'bfqq->bic'"), bic->bfqq will be accessed in bic_set_bfqq(), however, in some context bic->bfqq will be freed, and bic_set_bfqq() is called with the freed bic->bfqq. Fix the problem by always freeing bfqq after bic_set_bfqq().
Quoted source text, attributed separately from HOL analysis.