CVE-2026-46230: Linux kernel · drm/amdgpu/vcn3: Prevent OOB reads when parsing dec msg
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 7.1 High · fixed in f55552adb100eb54a6e6dabff4fbdc8679bd3fa0 : patch Linux kernel soon.
Data as of 26 Oct 2026, 14:18 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in f55552adb100eb54a6e6dabff4fbdc8679bd3fa0, e382e0b81a3e7bd21504fee1d01ae8b08f84d3a7, b193019860d61e92da395eae2011f2f6716b182f +4
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 28 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/vcn3: Prevent OOB reads when parsing dec msg Check bounds against the end of the BO whenever we access the msg.
References
- git.kernel.org/stable/c/f55552adb100eb54a6e6dabff4fbdc8679bd3fa0 (opens in a new tab)
- git.kernel.org/stable/c/82c535eff05490c71153af57de9fe85502fcb5d5 (opens in a new tab)
- git.kernel.org/stable/c/638d3e0b9eb77aa53fdd60e2b928761d16ba76fa (opens in a new tab)
- git.kernel.org/stable/c/870c8738c3774336baedddd0240951d078a703b8 (opens in a new tab)
- git.kernel.org/stable/c/638e48ee39d0f2af9336f917a6f5d6692dd64d93 (opens in a new tab)
- git.kernel.org/stable/c/e382e0b81a3e7bd21504fee1d01ae8b08f84d3a7 (opens in a new tab)
- git.kernel.org/stable/c/b193019860d61e92da395eae2011f2f6716b182f (opens in a new tab)