LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23063: uacce: ensure safe queue release with state management

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-23063 is a Linux kernel bug in UACCE queue cleanup. In a narrow shutdown/removal race, the kernel can dereference a freed or NULL operations pointer. The practical business risk is likely service disruption on systems using UACCE-backed accelerators, not confirmed data theft or remote compromise.

Executive priority

Treat as a targeted availability risk for accelerator-enabled Linux environments. Prioritize patching where virtualization, forced shutdown workflows, or hardware accelerator workloads are business-critical. For general Linux fleets without UACCE usage, handle through normal kernel maintenance after confirming exposure.

Technical view

The flaw affects UACCE queue lifecycle handling. During forced poweroff in a virtualized environment while accelerators are active, uacce_fops_release and uacce_remove may run concurrently. The fix adds queue state checks and separates stop_queue from final put_queue release to avoid accessing freed ops pointers.

Likely exposure

Exposure appears limited to Linux systems using the UACCE accelerator framework or related hardware drivers. Standard systems without UACCE-enabled accelerators are less likely to be exposed. The bundle does not provide distro-specific package mappings.

Exploitation context

The source bundle does not show active exploitation, and KEV is false. The described trigger involves forced poweroff in a virtualized environment while accelerators are still working, suggesting a race-condition denial-of-service scenario rather than a broadly reachable attack path.

Researcher notes

Evidence supports a kernel race in resource release, fixed by queue state management. The bundle lacks CVSS, CWE, exploit reports, and distro package details. Do not assume remote exploitability or privilege impact beyond the described NULL pointer access without additional vendor analysis.

Mitigation direction

  • Update to a Linux kernel or distribution package containing the referenced stable fixes.
  • Check your Linux vendor advisory for exact affected and fixed package versions.
  • If UACCE accelerators are unused, consider disabling related drivers or hardware exposure.
  • Avoid forced shutdown of guests while accelerator workloads are active where operationally feasible.

Validation and detection

  • Inventory hosts and guests using UACCE or accelerator devices.
  • Map running kernel versions against vendor advisories for CVE-2026-23063.
  • Confirm patched kernels include the referenced UACCE queue lifecycle change.
  • Review crash logs for NULL ops pointer faults in UACCE cleanup paths.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23063 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
8Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux015d239ac0142ad0e26567fd890ef8d171f13709, 015d239ac0142ad0e26567fd890ef8d171f13709, 015d239ac0142ad0e26567fd890ef8d171f13709, 015d239ac0142ad0e26567fd890ef8d171f13709, 015d239ac0142ad0e26567fd890ef8d171f13709, 015d239ac0142ad0e26567fd890ef8d171f13709, 015d239ac0142ad0e26567fd890ef8d171f13709unaffected
LinuxLinux5.7, 0, 5.10.249, 5.15.199, 6.1.162, 6.6.122, 6.12.68, 6.18.8, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.