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-23463soc: fsl: qbman: fix race condition in qman_destroy_fq

Description

In the Linux kernel, the following vulnerability has been resolved: soc: fsl: qbman: fix race condition in qman_destroy_fq When QMAN_FQ_FLAG_DYNAMIC_FQID is set, there's a race condition between fq_table[fq->idx] state and freeing/allocating from the pool and WARN_ON(fq_table[fq->idx]) in qman_create_fq() gets triggered. Indeed, we can have: Thread A Thread B qman_destroy_fq() qman_create_fq() qman_release_fqid() qman_shutdown_fq() gen_pool_free() -- At this point, the fqid is available again -- qman_alloc_fqid() -- so, we can get the just-freed fqid in thread B -- fq->fqid = fqid; fq->idx = fqid * 2; WARN_ON(fq_table[fq->idx]); fq_table[fq->idx] = fq; fq_table[fq->idx] = NULL; And adding some logs between qman_release_fqid() and fq_table[fq->idx] = NULL makes the WARN_ON() trigger a lot more. To prevent that, ensure that fq_table[fq->idx] is set to NULL before gen_pool_free() is called by using smp_wmb().

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 7 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-23463, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.10% · top 99% of all CVEs (14 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected c535e923bb97a4b361e89a6383693482057f8b0c – < 66442cf9989bd4489fa80d9f37637d58ab016835
    • affected c535e923bb97a4b361e89a6383693482057f8b0c – < d288fbe652ef43b7128e4bc0c0c2ef6bd03a2210
    • affected c535e923bb97a4b361e89a6383693482057f8b0c – < 9e3d47904b8153c8c3ad2f9b66d5008aad677aa8
    • affected c535e923bb97a4b361e89a6383693482057f8b0c – < d21923a8059fa896bfef016f55dd769299335cb4
    • affected c535e923bb97a4b361e89a6383693482057f8b0c – < 751f60bd48edaf03f9d84ab09e5ce6705757d50f
    • affected c535e923bb97a4b361e89a6383693482057f8b0c – < 85dbbf7dc88b0a54f2e334daedf6f3f31fd004fa
    • affected c535e923bb97a4b361e89a6383693482057f8b0c – < 265e56714635c5dd1e5964bfd97fa6e73f62cde5
    • affected c535e923bb97a4b361e89a6383693482057f8b0c – < 014077044e874e270ec480515edbc1cadb976cf2
  • Linux · Linux

    • affected 4.9
    • unaffected < 4.9
    • unaffected 5.10.253 – ≤ 5.10.*
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.167 – ≤ 6.1.*
    • unaffected 6.6.130 – ≤ 6.6.*
    • unaffected 6.12.78 – ≤ 6.12.*
    • unaffected 6.18.20 – ≤ 6.18.*
    • unaffected 6.19.10 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References11

Sources

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

Badge for a README or a ticket

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

Record last updated .