[CVE-2026-46235][LOW] media: saa7164: add ioremap return checks and cleanups

[CVE-2026-46235][LOW] media: saa7164: add ioremap return checks and cleanups

[AL-KERNEL]

CVE: CVE-2026-46235
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: media: saa7164: add ioremap return checks and cleanups
Commit: 3ce8f3057c51bb0a66aa3fab0862be74e9f88684
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=3ce8f3057c51bb0a66aa3fab0862be74e9f88684
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-46235
Analysis date: Thu, 28 May 2026 06:56:44 -0400
ActionableScore: 0
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
Unchecked PCI BAR MMIO mapping failures in the saa7164 driver could cause a NULL pointer dereference during device setup, but triggering is hardware and admin controlled and the impact is DoS only.

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

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

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-46235	LOW	CHECK	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';**CWE-476;CWE-252;CWE-703;BEST CVSS score: '4.1';DESCR 'saa7164_dev_setup() did not check whether PCI BAR0 or BAR2 MMIO mapping succeeded before continuing device initialization. If pci_ioremap_bar failed, later driver code could dereference a NULL MMIO pointer and crash the kernel during probe or setup. For the CVSS the PR:H is used because triggering this path typically requires administrative control over driver loading, PCI device probing, or the host hardware environment. The issue is not network reachable and is tied to a specific PCI media driver and rare mapping failure conditions. Impact is denial of service only, with no supported evidence of information disclosure or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 0)	YES	LOCK NULLPTR ERRORPATH HARDWARE LINUS 	NO	NO	checked

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

ActionableScore=0

## 1. ActionableScore

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

## 2. Signal breakdown

Triggered positive signals:

* Reliable kernel crash / strong DoS: +1
  If BAR0 or BAR2 MMIO mapping fails and the driver continues initialization, later code may dereference a NULL MMIO pointer and crash the kernel.

Triggered negative signals:

* Requires admin/root/CAP_SYS_ADMIN or equivalent in typical deployments: -2
  Realistic triggering requires driver loading, PCI probe manipulation, or host device-management control.

* Physical-only or rare hardware-only condition: -2
  The issue depends on a specific saa7164 PCI media device and an ioremap failure during probe.

* Rare and difficult-to-reach subsystem/configuration: -1
  This is a device-specific media PCI driver path, not a broad kernel interface.

Net score is clamped to 0.

## 3. Reachability analysis

The bug is reachable during saa7164 device setup when PCI BAR MMIO remapping fails. A normal local unprivileged user generally cannot force this path in typical deployments. Namespaces or containers do not materially lower the requirement unless the environment already delegates dangerous device-management or PCI hotplug capabilities. The path is not network reachable and is not default-reachable without the relevant hardware and driver.

## 4. Severity interpretation

This behaves like a Low-like or ordinary Moderate robustness issue. The realistic impact is denial of service from a NULL pointer dereference during driver probe or initialization failure. There is no supported UAF, OOB write, type confusion, attacker-controlled overwrite, information disclosure, or privilege escalation primitive in the patch context.

## 5. One-sentence report phrase

Unchecked PCI BAR MMIO mapping failures in the saa7164 driver could cause a NULL pointer dereference during device setup, but triggering is hardware and admin controlled and the impact is DoS only.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

Reason: this is a rare PCI driver probe NULL dereference with PR:H-like practical requirements, no network reachability, and no memory corruption primitive beyond crash.

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

Patch: media: saa7164: add ioremap return checks and cleanups
Commit: 3ce8f3057c51bb0a66aa3fab0862be74e9f88684
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=3ce8f3057c51bb0a66aa3fab0862be74e9f88684

Commit description:

Add checks for ioremap return values in saa7164_dev_setup(). If
ioremap for BAR0 or BAR2 fails, release the already allocated PCI
memory regions, remove the device from the global list, decrement
the device count, and return -ENODEV.

This prevents potential null pointer dereferences and ensures proper
cleanup on memory mapping failures.

Fixes: 443c122 ("V4L/DVB (12923): SAA7164: Add support for the NXP SAA7164 silicon")
Cc: stable@vger.kernel.org
Signed-off-by: Wang Jun <1742789905@qq.com>
Signed-off-by: Hans Verkuil <hverkuil+cisco@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/media/pci/saa7164/saa7164-core.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=3ce8f3057c51bb0a66aa3fab0862be74e9f88684

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

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

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: Not available
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.1

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