CVE-2026-23338
published 2026-03-25CVE-2026-23338: In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/userq: Do not allow userspace to trivially triger kernel warnings Userspace can…
PriorityP418medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.12%
2.2th percentile
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)
Affected
12 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.19.8-1 (forky) | linux 6.19.8-1 (forky) |
| linux | linux | — | — |
| linux | linux | >= a292fdecd72834b3bec380baa5db1e69e7f70679 < 1753f5f81ab60a553287f9ee659a6ac363adf8d7 | 1753f5f81ab60a553287f9ee659a6ac363adf8d7 |
| linux | linux | >= a292fdecd72834b3bec380baa5db1e69e7f70679 < 7321302edca3a349ddaea689df95b986beee6c4a | 7321302edca3a349ddaea689df95b986beee6c4a |
| linux | linux | >= a292fdecd72834b3bec380baa5db1e69e7f70679 < 7b7d7693a55d606d700beb9549c9f7f0e5d9c24f | 7b7d7693a55d606d700beb9549c9f7f0e5d9c24f |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 6.19.8-1 | 6.19.8-1 |
| linux | linux_kernel | >= 6.16.0 < 6.18.17 | 6.18.17 |
| linux | linux_kernel | >= 6.16.1 < 6.18.17 | 6.18.17 |
| linux | linux_kernel | >= 6.19 < 6.19.7 | 6.19.7 |
| linux | linux_kernel | >= 6.19.0 < 6.19.7 | 6.19.7 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: drm/amdgpu/userq: Do not allow userspace to trivially triger kernel warnings
vendor_redhat·2026-03-25
CVE-2026-23338 CWE-1284 kernel: drm/amdgpu/userq: Do not allow userspace to trivially triger kernel warnings
kernel: drm/amdgpu/userq: Do not allow userspace to trivially triger kernel warnings
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)
A flaw was found in the Linux kernel, specifically within the `drm/amdgpu/userq` component. This vulnerability allows a local user to intentional
Debian
CVE-2026-23338: linux - In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/...
vendor_debian·2026
CVE-2026-23338 [LOW] CVE-2026-23338: linux - In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/...
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)
Scope: local
bookworm: resolved
bullseye: resolved
forky: resolved (fixed in 6.19.8-1)
sid: resolved (fixed in 6.19.8-1)
trixie: resolved
OSV
drm/amdgpu/userq: Do not allow userspace to trivially triger kernel warnings
osv·2026-03-25
CVE-2026-23338 drm/amdgpu/userq: Do not allow userspace to trivially triger kernel warnings
drm/amdgpu/userq: Do not allow userspace to trivially triger kernel warnings
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)
OSV
CVE-2026-23338: In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/userq: Do not allow userspace to trivially triger kernel warnings Users
osv·2026-03-25
CVE-2026-23338 CVE-2026-23338: In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/userq: Do not allow userspace to trivially triger kernel warnings Users
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)
GHSA
GHSA-ggpq-p67g-h639: In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu/userq: Do not allow userspace to trivially triger kernel warnings
Use
ghsa_unreviewed·2026-03-25
CVE-2026-23338 GHSA-ggpq-p67g-h639: In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu/userq: Do not allow userspace to trivially triger kernel warnings
Use
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)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2026-23338 kernel: drm/amdgpu/userq: Do not allow userspace to trivially triger kernel warnings
bugzilla·2026-03-25·CVSS 5.5
CVE-2026-23338 [MEDIUM] CVE-2026-23338 kernel: drm/amdgpu/userq: Do not allow userspace to trivially triger kernel warnings
CVE-2026-23338 kernel: drm/amdgpu/userq: Do not allow userspace to trivially triger kernel warnings
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)
Discussion:
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026032534-CVE-2026-23338-67c7@gregkh/T
Wiz
CVE-2026-23338 Impact, Exploitability, and Mitigation Steps | Wiz
blogs_wiz·CVSS 5.3
CVE-2026-23338 [MEDIUM] CVE-2026-23338 Impact, Exploitability, and Mitigation Steps | Wiz
## CVE-2026-23338 :
Linux Debian vulnerability analysis and mitigation
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)
Source : NVD
Published March 25, 2026
CNA Score N/A
Affected Technologies
Linux Debian
Linux Ubuntu
Has Public Exploit No
Has CISA KEV Exploit No
C
2026-03-25
Published