CVE-2026-23170

N/A Unknown

📋 TL;DR

This CVE describes a resource leak vulnerability in the Linux kernel's DRM/iMX TVE driver where a reference to the DDC (Display Data Channel) device is not properly released during probe failure or driver unbind. This affects Linux systems using the i.MX platform with the DRM/iMX TVE driver. The vulnerability could lead to resource exhaustion over time.

💻 Affected Systems

Products:
  • Linux kernel with DRM/iMX TVE driver
Versions: Specific kernel versions containing the vulnerable code (exact range requires checking git commits)
Operating Systems: Linux distributions using affected kernel versions
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects systems with i.MX platform hardware using the DRM/iMX TVE driver. Not all Linux systems are vulnerable.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Sustained exploitation could lead to kernel memory exhaustion, causing system instability, denial of service, or potential kernel crashes.

🟠

Likely Case

Gradual resource leakage during repeated probe/unbind cycles, potentially leading to system performance degradation or driver failures.

🟢

If Mitigated

Minimal impact with proper monitoring and system maintenance; resource leaks would be limited and detectable.

🌐 Internet-Facing: LOW - This is a local kernel driver issue requiring local access or specific hardware interaction.
🏢 Internal Only: MEDIUM - Could affect systems with i.MX hardware running vulnerable kernel versions, particularly those frequently loading/unloading the TVE driver.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Exploitation requires local access and ability to trigger the vulnerable code path through driver operations. No known public exploits.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Kernel versions containing the fix commits: 4aaff8f6ab38f81e00ab8aa1fcfb7eb20cd87ba1, 52755c5680ce333b33d0750a200fbc99420ed2b2, 77365382585b40559d63538d09e26e4b2af28fbc, 9a15d3fdc22d48f597792aee0cf1bf0947fc62e6, ca68745e820ecd210e3ab018497c9e6b69025c4b

Vendor Advisory: https://git.kernel.org/stable/c/

Restart Required: Yes

Instructions:

1. Update to a kernel version containing the fix commits. 2. Check with your distribution vendor for backported patches. 3. Reboot the system after kernel update.

🔧 Temporary Workarounds

Disable TVE driver if not needed

Linux

Prevent loading of the vulnerable driver module

echo 'blacklist imx_drm_tve' >> /etc/modprobe.d/blacklist.conf
rmmod imx_drm_tve

🧯 If You Can't Patch

  • Monitor system memory and resource usage for unusual patterns
  • Restrict local access to systems with i.MX hardware

🔍 How to Verify

Check if Vulnerable:

Check if the system uses i.MX hardware and has the TVE driver loaded: 'lsmod | grep imx_drm_tve' and check kernel version

Check Version:

uname -r

Verify Fix Applied:

Verify kernel version includes the fix commits or check with distribution vendor for patch status

📡 Detection & Monitoring

Log Indicators:

  • Kernel oops messages
  • Memory allocation failures in kernel logs
  • Driver probe/unbind errors

Network Indicators:

  • None - this is a local kernel issue

SIEM Query:

Search for kernel logs containing 'imx_drm_tve', 'DDC', or memory allocation failures

🔗 References

📤 Share & Export