CVE-2025-38336: Linux kernel · ata: pata_via: Force PIO for ATAPI devices on VT6415/VT6330
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 5.15.0-1092.99~20.04.1 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.15.0-1092.99~20.04.1, 5.15.0-1096.105~20.04.1, 5.15.0-1114.123~20.04.1 +60
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Jul 2025
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.
Patches and advisories
- ubuntu.com/security/notices/USN-7774-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7774-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7774-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7775-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7776-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7775-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7775-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7774-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7774-5 (opens in a new tab)
- ubuntu.com/security/notices/USN-7833-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7834-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7833-2 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 25.10linux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-aws-6.14pkg:deb/ubuntu/linux-aws-6.14?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
In the Linux kernel, the following vulnerability has been resolved: ata: pata_via: Force PIO for ATAPI devices on VT6415/VT6330 The controller has a hardware bug that can hard hang the system when doing ATAPI DMAs without any trace of what happened. Depending on the device attached, it can also prevent the system from booting. In this case, the system hangs when reading the ATIP from optical media with cdrecord -vvv -atip on an _NEC DVD_RW ND-4571A 1-01 and an Optiarc DVD RW AD-7200A 1.06 attached to an ASRock 990FX Extreme 4, running at UDMA/33. The issue can be reproduced by running the same command with a cygwin build of cdrecord on WinXP, although it requires more attempts to cause it. The hang in that case is also resolved by forcing PIO. It doesn't appear that VIA has produced any drivers for that OS, thus no known workaround exists. HDDs attached to the controller do not suffer from any DMA issues.
References
- ubuntu.com/security/CVE-2025-38336 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2025-38336 (opens in a new tab)
- git.kernel.org/linus/d29fc02caad7f94b62d56ee1b01c954f9c961ba7 (opens in a new tab)
- git.kernel.org/stable/c/0d9a48dfa934f43ac839211ae4aeba34f666a9a5 (opens in a new tab)
- git.kernel.org/stable/c/67d66a5e4583fd3bcf13d6f747e571df13cbad51 (opens in a new tab)
- git.kernel.org/stable/c/7fc89c218fc96a296a2840b1e37f4e0975f7a108 (opens in a new tab)
- git.kernel.org/stable/c/8212cd92fe40aae6fe5a073bc70e758c42bb4bfc (opens in a new tab)
- git.kernel.org/stable/c/8edfed4439b107d62151ff6c075958d169da3e71 (opens in a new tab)
- git.kernel.org/stable/c/947f9304d3c876c6672b947b80c0ef51161c6d2f (opens in a new tab)
- git.kernel.org/stable/c/bb7212ee4ff086628a2c1c22336d082a87cb893d (opens in a new tab)
- git.kernel.org/stable/c/d29fc02caad7f94b62d56ee1b01c954f9c961ba7 (opens in a new tab)
- ubuntu.com/security/notices/USN-7774-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7774-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7774-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7775-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7776-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7775-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7775-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7774-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7774-5 (opens in a new tab)