CVE-2026-23063
What it is
In the Linux kernel, the following vulnerability has been resolved: uacce: ensure safe queue release with state management Directly calling `put_queue` carries risks since it cannot guarantee that resources of `uacce_queue` have been fully released beforehand. So adding a `stop_queue` operation for the UACCE_CMD_PUT_Q command and leaving the `put_queue` operation to the final resource release ensures safety. Queue states are defined as follows: - UACCE_Q_ZOMBIE: Initial state - UACCE_Q_INIT: After opening `uacce` - UACCE_Q_STARTED: After `start` is issued via `ioctl` When executing `poweroff -f` in virt while accelerator are still working, `uacce_fops_release` and `uacce_remove` may execute concurrently. This can cause `uacce_put_queue` within `uacce_fops_release` to access a NULL `ops` pointer. Therefore, add state checks to prevent accessing freed pointers.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-476 · NULL pointer dereference
- Record status
- Analyzed
Affected
- Linux Kernel < 5.10.249
- Linux Kernel < 5.15.199
- Linux Kernel < 6.1.162
- Linux Kernel < 6.6.122
- Linux Kernel < 6.12.68
- Linux Kernel < 6.18.8
- Linux Kernel 6.19
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-23063.md and follow it. Check whether this project is affected by CVE-2026-23063. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/26c08dabe5475d99a13f353d8dd70e518de45663
- https://git.kernel.org/stable/c/336fb41a186e7c0415ae94fec9e23d1f04b87483
- https://git.kernel.org/stable/c/43f233eb6e7b9d88536881a9bc43726d0e34800d
- https://git.kernel.org/stable/c/47634d70073890c9c37e39ab4ff93d4b585b028a
- https://git.kernel.org/stable/c/8b57bf1d3b1db692f34bce694a03e41be79f6016
- https://git.kernel.org/stable/c/92e4f11e29b98ef424ff72d6371acac03e5d973c
- https://git.kernel.org/stable/c/b457abeb5d962db88aaf60e249402fd3073dbfab
References
- https://git.kernel.org/stable/c/26c08dabe5475d99a13f353d8dd70e518de45663
- https://git.kernel.org/stable/c/336fb41a186e7c0415ae94fec9e23d1f04b87483
- https://git.kernel.org/stable/c/43f233eb6e7b9d88536881a9bc43726d0e34800d
- https://git.kernel.org/stable/c/47634d70073890c9c37e39ab4ff93d4b585b028a
- https://git.kernel.org/stable/c/8b57bf1d3b1db692f34bce694a03e41be79f6016
- https://git.kernel.org/stable/c/92e4f11e29b98ef424ff72d6371acac03e5d973c
- https://git.kernel.org/stable/c/b457abeb5d962db88aaf60e249402fd3073dbfab