Answer in brief
CVE-2026-23463 records a Medium severity (CVSS 4.7) vulnerability in soc: fsl: qbman: fix race condition in qman_destroy_fq. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-23463 records a Medium severity (CVSS 4.7) vulnerability in soc: fsl: qbman: fix race condition in qman_destroy_fq. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 4.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c535e923bb97a4b361e89a6383693482057f8b0c <66442cf9989bd4489fa80d9f37637d58ab016835 || >=c535e923bb97a4b361e89a6383693482057f8b0c <d288fbe652ef43b7128e4bc0c0c2ef6bd03a2210 || >=c535e923bb97a4b361e89a6383693482057f8b0c <9e3d47904b8153c8c3ad2f9b66d5008aad677aa8 || >=c535e923bb97a4b361e89a6383693482057f8b0c <d21923a8059fa896bfef016f55dd769299335cb4 || >=c535e923bb97a4b361e89a6383693482057f8b0c <751f60bd48edaf03f9d84ab09e5ce6705757d50f || >=c535e923bb97a4b361e89a6383693482057f8b0c <85dbbf7dc88b0a54f2e334daedf6f3f31fd004fa || >=c535e923bb97a4b361e89a6383693482057f8b0c <265e56714635c5dd1e5964bfd97fa6e73f62cde5 || >=c535e923bb97a4b361e89a6383693482057f8b0c <014077044e874e270ec480515edbc1cadb976cf2 | 66442cf9989bd4489fa80d9f37637d58ab016835, d288fbe652ef43b7128e4bc0c0c2ef6bd03a2210, 9e3d47904b8153c8c3ad2f9b66d5008aad677aa8, d21923a8059fa896bfef016f55dd769299335cb4, 751f60bd48edaf03f9d84ab09e5ce6705757d50f, 85dbbf7dc88b0a54f2e334daedf6f3f31fd004fa, 265e56714635c5dd1e5964bfd97fa6e73f62cde5, 014077044e874e270ec480515edbc1cadb976cf2 |
| Linux/Linuxgeneric | 4.9 | Not reported |
| Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
| Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.5 <* | * |
| Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
| Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric | >=V3.1.5 <* | * |
| Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.5 <* | * |
| Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
Published upstream
Apr 3, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 14, 2026
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().
Quoted source text, attributed separately from HOL analysis.
CVSS is 4.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c535e923bb97a4b361e89a6383693482057f8b0c <66442cf9989bd4489fa80d9f37637d58ab016835 || >=c535e923bb97a4b361e89a6383693482057f8b0c <d288fbe652ef43b7128e4bc0c0c2ef6bd03a2210 || >=c535e923bb97a4b361e89a6383693482057f8b0c <9e3d47904b8153c8c3ad2f9b66d5008aad677aa8 || >=c535e923bb97a4b361e89a6383693482057f8b0c <d21923a8059fa896bfef016f55dd769299335cb4 || >=c535e923bb97a4b361e89a6383693482057f8b0c <751f60bd48edaf03f9d84ab09e5ce6705757d50f || >=c535e923bb97a4b361e89a6383693482057f8b0c <85dbbf7dc88b0a54f2e334daedf6f3f31fd004fa || >=c535e923bb97a4b361e89a6383693482057f8b0c <265e56714635c5dd1e5964bfd97fa6e73f62cde5 || >=c535e923bb97a4b361e89a6383693482057f8b0c <014077044e874e270ec480515edbc1cadb976cf2 | 66442cf9989bd4489fa80d9f37637d58ab016835, d288fbe652ef43b7128e4bc0c0c2ef6bd03a2210, 9e3d47904b8153c8c3ad2f9b66d5008aad677aa8, d21923a8059fa896bfef016f55dd769299335cb4, 751f60bd48edaf03f9d84ab09e5ce6705757d50f, 85dbbf7dc88b0a54f2e334daedf6f3f31fd004fa, 265e56714635c5dd1e5964bfd97fa6e73f62cde5, 014077044e874e270ec480515edbc1cadb976cf2 |
| Linux/Linuxgeneric | 4.9 | Not reported |
| Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
| Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.5 <* | * |
| Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
| Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric | >=V3.1.5 <* | * |
| Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.5 <* | * |
| Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
Published upstream
Apr 3, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 14, 2026
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().
Quoted source text, attributed separately from HOL analysis.