Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 22 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-23063, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.15% · top 96% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 015d239ac0142ad0e26567fd890ef8d171f13709 – < b457abeb5d962db88aaf60e249402fd3073dbfab
    • affected 015d239ac0142ad0e26567fd890ef8d171f13709 – < 8b57bf1d3b1db692f34bce694a03e41be79f6016
    • affected 015d239ac0142ad0e26567fd890ef8d171f13709 – < 336fb41a186e7c0415ae94fec9e23d1f04b87483
    • affected 015d239ac0142ad0e26567fd890ef8d171f13709 – < 43f233eb6e7b9d88536881a9bc43726d0e34800d
    • affected 015d239ac0142ad0e26567fd890ef8d171f13709 – < 47634d70073890c9c37e39ab4ff93d4b585b028a
    • affected 015d239ac0142ad0e26567fd890ef8d171f13709 – < 92e4f11e29b98ef424ff72d6371acac03e5d973c
    • affected 015d239ac0142ad0e26567fd890ef8d171f13709 – < 26c08dabe5475d99a13f353d8dd70e518de45663
  • Linux · Linux

    • affected 5.7
    • unaffected < 5.7
    • unaffected 5.10.249 – ≤ 5.10.*
    • unaffected 5.15.199 – ≤ 5.15.*
    • unaffected 6.1.162 – ≤ 6.1.*
    • unaffected 6.6.122 – ≤ 6.6.*
    • unaffected 6.12.68 – ≤ 6.12.*
    • unaffected 6.18.8 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-23063 badge
[![CVE-2026-23063](https://cveledger.app/badge/CVE-2026-23063.svg)](https://cveledger.app/cve/CVE-2026-23063)

Record last updated .