CVE-2026-23463
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().
EPSS 0.01% · 2.7th percentile
Risk Scores
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| linux | linux_kernel | 4.9, 4.9, 4.9 |
| Linux | Linux | c535e923bb97a4b361e89a6383693482057f8b0c, c535e923bb97a4b361e89a6383693482057f8b0c, c535e923bb97a4b361e89a6383693482057f8b0c |
Timeline
- Apr 3, 2026 CVE Published
- May 18, 2026 EPSS Score
- May 19, 2026 EPSS Score
- May 20, 2026 EPSS Score
- May 20, 2026 CVE Updated
- May 21, 2026 EPSS Score
- May 22, 2026 EPSS Score
- May 23, 2026 EPSS Score
- May 24, 2026 EPSS Score
- May 25, 2026 EPSS Score
- May 26, 2026 EPSS Score
- May 27, 2026 EPSS Score
References
- https://git.kernel.org/stable/c/9e3d47904b8153c8c3ad2f9b66d5008aad677aa8 url
- https://git.kernel.org/stable/c/d21923a8059fa896bfef016f55dd769299335cb4 url
- https://git.kernel.org/stable/c/751f60bd48edaf03f9d84ab09e5ce6705757d50f url
- https://git.kernel.org/stable/c/85dbbf7dc88b0a54f2e334daedf6f3f31fd004fa url
- https://git.kernel.org/stable/c/265e56714635c5dd1e5964bfd97fa6e73f62cde5 url
- https://git.kernel.org/stable/c/014077044e874e270ec480515edbc1cadb976cf2 url
- https://lists.debian.org/debian-lts-announce/2026/05/msg00004.html advisory
- https://lists.debian.org/debian-lts-announce/2026/05/msg00005.html advisory
- https://lists.debian.org/debian-security-announce/2026/msg00154.html advisory
- https://lists.debian.org/debian-security-announce/2026/msg00148.html advisory
- https://lists.debian.org/debian-lts-announce/2026/05/msg00051.html advisory
- https://lists.debian.org/debian-lts-announce/2026/05/msg00052.html advisory
- https://www.suse.com/support/update/announcement/2026/suse-su-202621930-1 advisory
- https://www.suse.com/support/update/announcement/2026/suse-su-202621841-1 advisory
- https://www.suse.com/support/update/announcement/2026/suse-su-20262238-1 advisory
- https://www.suse.com/support/update/announcement/2026/suse-su-202621974-1 advisory
- https://www.suse.com/support/update/announcement/2026/suse-su-20262217-1 advisory
- https://www.suse.com/support/update/announcement/2026/suse-su-202621979-1 advisory
- https://www.suse.com/support/update/announcement/2026/suse-su-20262149-1 advisory
- https://www.suse.com/support/update/announcement/2026/suse-su-20262158-1 advisory
…and 55 more