Null Pointer Dereference in Linux Kernel Intel IPU6 Driver

Publication date: 2026-06-08

Last updated on: 2026-07-08

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: media: intel/ipu6: fix error pointer dereference In a error path isp->psys is confirmed to be an error pointer not NULL so this condition is true and the error pointer is dereferenced. So isp-psys should be set to NULL before going to out_ipu6_bus_del_devices. Detected by Smatch: drivers/media/pci/intel/ipu6/ipu6.c:690 ipu6_pci_probe() error: 'isp->psys' dereferencing possible ERR_PTR() [Sakari Ailus: Fix commit message.]

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-06-08

Last Modified

2026-07-08

Generated

2026-07-19

AI Q&A

2026-06-08

EPSS Evaluated

2026-07-18

NVD

CVE-2026-46313

EUVD

EUVD-2026-35123

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	From 6.13 (inc) to 6.18.32 (exc)
linux	linux_kernel	From 6.19 (inc) to 7.0.9 (exc)
linux	linux_kernel	From 6.10 (inc) to 6.12.90 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-476	The product dereferences a pointer that it expects to be valid but is NULL.

Attack-Flow Graph

Executive Summary

This vulnerability exists in the Linux kernel's Intel IPU6 media driver. It involves an error pointer dereference where the code mistakenly treats an error pointer as a valid pointer. Specifically, the 'isp->psys' pointer is confirmed to be an error pointer rather than NULL, but the code dereferences it anyway, which can lead to unexpected behavior or crashes. The fix involves setting 'isp->psys' to NULL before proceeding to device cleanup to avoid dereferencing the error pointer.

Impact Analysis

Dereferencing an error pointer can cause the system to behave unpredictably, potentially leading to kernel crashes or denial of service conditions. This can affect system stability and reliability, especially on systems using the Intel IPU6 media driver.

Hi! I’m here to help you understand CVE-2026-46313. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70