Answer in brief
CVE-2026-23338 records a Unknown severity vulnerability in drm/amdgpu/userq: Do not allow userspace to trivially triger kernel warnings. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a292fdecd72834b3bec380baa5db1e69e7f70679 <1753f5f81ab60a553287f9ee659a6ac363adf8d7 || >=a292fdecd72834b3bec380baa5db1e69e7f70679 <7321302edca3a349ddaea689df95b986beee6c4a || >=a292fdecd72834b3bec380baa5db1e69e7f70679 <7b7d7693a55d606d700beb9549c9f7f0e5d9c24f | 1753f5f81ab60a553287f9ee659a6ac363adf8d7, 7321302edca3a349ddaea689df95b986beee6c4a, 7b7d7693a55d606d700beb9549c9f7f0e5d9c24f |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
Mar 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/userq: Do not allow userspace to trivially triger kernel warnings Userspace can either deliberately pass in the too small num_fences, or the required number can legitimately grow between the two calls to the userq wait ioctl. In both cases we do not want the emit the kernel warning backtrace since nothing is wrong with the kernel and userspace will simply get an errno reported back. So lets simply drop the WARN_ONs. (cherry picked from commit 2c333ea579de6cc20ea7bc50e9595ef72863e65c)
Quoted source text, attributed separately from HOL analysis.