CVE-2026-98782: Linux kernel · drm/mediatek: Fix ovl adaptor platform device leak
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 629458b7e49559593823e351535294db17331be7 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:18 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 629458b7e49559593823e351535294db17331be7, 048739be3e9cacae5301b68245668002fe6f0ce5, 8e3a350075b556f2fed4517705935bfee4529fb6 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 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/mediatek: Fix ovl adaptor platform device leak mtk_drm_probe() creates an OVL adaptor platform device with platform_device_register_data() when the display pipeline requires the OVL adaptor. If a later initialization step fails, the probe error path releases the DRM resources without unregistering the already registered OVL adaptor device. The normal remove path likewise leaves the device registered after the DRM driver is unbound. Keep track of whether the OVL adaptor was successfully registered and unregister it on probe failure. Also recover the platform device from the stored DDP component device and unregister it during normal removal. The issue was identified by a static analysis tool I developed and confirmed by manual review.
References
- git.kernel.org/stable/c/03fb1c657028cb9f189b400f3adb46e3ba676aa5 (opens in a new tab)
- git.kernel.org/stable/c/3d85bd738aba61df14dfaf8fe638e2172d8427bf (opens in a new tab)
- git.kernel.org/stable/c/629458b7e49559593823e351535294db17331be7 (opens in a new tab)
- git.kernel.org/stable/c/8e3a350075b556f2fed4517705935bfee4529fb6 (opens in a new tab)
- git.kernel.org/stable/c/048739be3e9cacae5301b68245668002fe6f0ce5 (opens in a new tab)