Linux Kernel up to 6.19.3 exynos vidi_connection_ioctl use after free

Summaryinfo

A vulnerability classified as critical has been found in Linux Kernel up to 6.19.3. This affects the function vidi_connection_ioctl of the component exynos. Performing a manipulation results in use after free. This vulnerability is known as CVE-2026-45956. No exploit is available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.19.3. It has been classified as critical. This affects the function vidi_connection_ioctl of the component exynos. The manipulation with an unknown input leads to a use after free vulnerability. CWE is classifying the issue as CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: drm/exynos: vidi: use priv->vidi_dev for ctx lookup in vidi_connection_ioctl() vidi_connection_ioctl() retrieves the driver_data from drm_dev->dev to obtain a struct vidi_context pointer. However, drm_dev->dev is the exynos-drm master device, and the driver_data contained therein is not the vidi component device, but a completely different device. This can lead to various bugs, ranging from null pointer dereferences and garbage value accesses to, in unlucky cases, out-of-bounds errors, use-after-free errors, and more. To resolve this issue, we need to store/delete the vidi device pointer in exynos_drm_private->vidi_dev during bind/unbind, and then read this exynos_drm_private->vidi_dev within ioctl() to obtain the correct struct vidi_context pointer.

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-45956 since 05/13/2026. The exploitability is told to be easy. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 06/07/2026).

Upgrading to version 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.18.14 or 6.19.4 eliminates this vulnerability. Applying the patch 2987642c5213508c6c9e718324c0d5289a92c474/65d1213baffa363f2eb1117b1dc7acc573b890f8/875fa28690e93ed5296c31d3344556c6bb867234/21ca24ba51a2c28bcc4df9d7e5a40b0eb66ab76d/b5fc86d753dd4c281a943b92f0eef02d31af03d7/a540f767642f75240a6c35f6a65b69e44cfcea9d/d3968a0d85b211e197f2f4f06268a7031079e0d0 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 5.10.252
• 5.15.202
• 6.1.166
• 6.6.129
• 6.18.0
• 6.18.1
• 6.18.2
• 6.18.3
• 6.18.4
• 6.18.5
• 6.18.6
• 6.18.7
• 6.18.8
• 6.18.9
• 6.18.10
• 6.18.11
• 6.18.12
• 6.18.13
• 6.19.0
• 6.19.1
• 6.19.2
• 6.19.3

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion