block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.15.87, 6.0.17, 6.1.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq Commit 64dc8c732f5c ("block, bfq: fix possible uaf for 'bfqq->bic'") will access 'bic->bfqq' in bic_set_bfqq(), however, bfq_exit_icq_bfqq() can free bfqq first, and then call bic_set_bfqq(), which will cause uaf. Fix the problem by moving bfq_exit_bfqq() behind bic_set_bfqq().
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 5533742c7cb1bc9b1f0bf401cc397d44a3a9e07a · fixed in 1425f1bb5df5239021fd09ebc2a5e8070e705d36; From 094f3d9314d67691cb21ba091c1b528f6e3c4893 · fixed in 7949b0df3dd9f4817ed4a4e989fa9ee81df6205f; From b22fd72bfebda3956efc4431b60ddfc0a51e03e0 · fixed in cfe5b38c37720313eff0dec5517442c7ab3c9a20; From 761564d93c8265f65543acf0a576b32d66bfa26a · fixed in 1ed959fef5b1c6f1a7a3fbea543698c30ebd6678; From 64dc8c732f5c2b406cc752e6aaa1bd5471159cab · fixed in 246cf66e300b76099b5dbd3fdd39e9a5dbc53f02
- Linux Linux
From 5.15.86 · fixed in 5.15.87; From 6.0.16 · fixed in 6.0.17; From 6.1.2 · fixed in 6.1.3
- KernelLinux
From 5.15.86 · fixed in 5.15.87; From 6.0.16 · fixed in 6.0.17; From 6.1.2 · fixed in 6.1.3