[CVE-2026-46313][LOW] media: intel/ipu6: fix error pointer dereference

[CVE-2026-46313][LOW] media: intel/ipu6: fix error pointer dereference

[AL-KERNEL]

CVE: CVE-2026-46313
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: media: intel/ipu6: fix error pointer dereference
Commit: fad134c446189e9bb48cea1a5ca426d2889a9c71
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=fad134c446189e9bb48cea1a5ca426d2889a9c71
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-46313
Analysis date: Mon, 08 Jun 2026 14:13:26 -0400
ActionableScore: 0
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
No one-sentence report phrase was found.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-46313 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-46313

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: LOW
Manual review required: NO

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-46313	LOW	CHECK	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H';**CWE-476;CWE-754;CWE-703;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.4';DESCR 'The IPU6 PCI probe error path can dereference an ERR_PTR stored in isp psys after a psys initialization failure. This happens when cleanup reaches out_ipu6_bus_del_devices and treats the error pointer as a valid object, which can lead to a kernel oops or crash during driver probing. The practical impact is denial of service only. For the CVSS the PR:H is used because reliable triggering normally requires administrative control over driver binding, module loading, PCI device probing, or a failing device setup path. The issue is not network reachable and does not provide a clear UAF, OOB write, or information leak primitive.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 0)  SKIP CVE-2026-46313  SKIP The Fixes patch not applied yet, so unlikely that actual: 25fedc021985a66a357a599ab771d6b495b6f78c YES  NO NO unknown 	MAYBE	SIMPLEFIX ERRORPATH HARDWARE 	-	-	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=0

1. ActionableScore
* Conservative score: 0
* Paranoid score: 0
* Final recommended bucket: **Ordinary Moderate / Low-like**::

2. Signal breakdown
* Reliable kernel crash / strong DoS: +1. ERR_PTR dereference in the IPU6 PCI probe cleanup path can cause a kernel oops or crash if the specific initialization failure path is reached.
* Requires admin/root/CAP_* in typical deployments: -2. Reliable triggering normally requires control over driver probing, module loading, PCI bind/unbind, or device initialization conditions.
* Physical-only or rare hardware-only condition: -2. The affected path is specific to Intel IPU6 PCI hardware and its driver initialization path.
* Score is floored at 0. No UAF, double free, OOB write, attacker-controlled overwrite, info leak, or policy bypass is supported by the patch.

3. Reachability analysis
The bug is triggered during IPU6 PCI driver probe cleanup after a failed psys initialization. In normal deployments, unprivileged local users cannot directly force PCI probe or driver bind/unbind operations. Containers and namespaces usually do not lower this requirement unless a container is unusually delegated direct device or driver-management privileges. The path is not network reachable and depends on specific Intel IPU6 hardware and driver configuration.

4. Severity interpretation
This behaves like a low-risk local privileged DoS, not an Important-class vulnerability. The theoretical impact is an invalid pointer dereference leading to crash, but there is no realistic evidence of memory lifetime corruption, reclaimable UAF, controlled write, data disclosure, or privilege escalation. The issue should not be treated as Actionable Moderate unless an environment exposes PCI driver management to less trusted users.

5. One-sentence report phrase
An IPU6 PCI probe error path may dereference an ERR_PTR during cleanup after psys initialization failure, causing a local privileged kernel crash with no supported confidentiality, integrity, or privilege-escalation primitive.

6. Manual review recommendation
NO MANUAL CHECK NEEDED. The patch fixes a straightforward ERR_PTR dereference in a hardware-specific privileged driver probe path, and the practical impact is limited to DoS under restricted triggering conditions.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: media: intel/ipu6: fix error pointer dereference
Commit: fad134c446189e9bb48cea1a5ca426d2889a9c71
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=fad134c446189e9bb48cea1a5ca426d2889a9c71

Commit description:

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()

Fixes: 25fedc0 ("media: intel/ipu6: add Intel IPU6 PCI device driver")
Cc: stable@vger.kernel.org
Signed-off-by: Ethan Tidmore <ethantidmore06@gmail.com>
[Sakari Ailus: Fix commit message.]
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/media/pci/intel/ipu6/ipu6.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=fad134c446189e9bb48cea1a5ca426d2889a9c71

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-46313 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-46313

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L
  The Best / paranoid CVSS vector: AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.4

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: unknown
  Paranoid ActionableScore: 0

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).