[CVE-2026-68205][MODERATE REGULAR] media: v4l2-fwnode: Fix subdev owner overwritten in v4l2_async_register_subdev_sensor() [ Upstream

[CVE-2026-68205][MODERATE REGULAR] media: v4l2-fwnode: Fix subdev owner overwritten in v4l2_async_register_subdev_sensor() [ Upstream

[AL-KERNEL]

CVE: CVE-2026-68205
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: media: v4l2-fwnode: Fix subdev owner overwritten in v4l2_async_register_subdev_sensor() [ Upstream
Commit: 47ef04cd13d38010b580056a9d8840aaab944841
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=47ef04cd13d38010b580056a9d8840aaab944841
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68205
Analysis date: Mon, 10 Aug 2026 18:27:00 -0400
ActionableScore: 4
ActionableScore lower bound: 2
Actionable bucket: Borderline Moderate / Manual review required
Manual review required: YES

Summary:
A V4L2 async sensor registration bug can overwrite the sensor subdev owner with the wrong module or NULL, allowing premature sensor module removal while notifier state still references the subdevice and creating a local use after free candidate with likely kernel crash impact.

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

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

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: MODERATE REGULAR
Manual review required: YES

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

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

CVE-2026-68205	MODERATE	CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:H';CWE-911;*CWE-416;*CWE-664;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.2';DESCR 'V4L2 async sensor registration can overwrite the sensor subdev owner with the v4l2-fwnode module or NULL when v4l2-fwnode is built in. This can prevent the real sensor driver module from being refcounted, so the sensor module may be removed while the subdevice is still referenced by an async notifier such as a CSI-2 receiver bridge. The resulting stale module lifetime can lead to a use after free candidate and at least a local denial of service via kernel crash. For the CVSS the PR:H is used in the paranoid score because reliable triggering normally requires module unload or driver lifecycle control such as CAP_SYS_MODULE. The issue is not network reachable. Impact is mainly availability, with limited confidentiality or integrity impact kept only for manual-review sensitivity because the bug class involves stale module references.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline Moderate / Manual review required (with actual score 3)	YES	INIT HARDWARE  INCREASED_FROM_LOW_BASED_ON_REQUIREMANUALCHECK DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	NO	NO	checked

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

ActionableScore=4
ActionableScoreLower=2

## 1. ActionableScore

* Conservative score: 2
* Paranoid score: 4
* Final recommended bucket: **Borderline Moderate / Manual review required**::

## 2. Signal breakdown

Conservative signals:

* Memory corruption, strong lifetime primitive: +2. The patch fixes a module owner reference bug that can allow premature sensor module removal while V4L2 async notifier state still references the subdevice.
* Real lifetime corruption: +1. This is a module refcount and object lifetime issue.
* Reliable kernel crash / strong DoS: +1. A stale subdevice or stale module callback after removal can plausibly crash the kernel.
* Requires admin/root/CAP_SYS_MODULE in typical deployments: -2. Reliable triggering normally requires unloading or controlling sensor driver modules.

Conservative total: 2

Paranoid additional signals:

* Weak LPE concern: +1. The bug involves stale module lifetime and possible callback use after module removal, but no controlled reclaim, arbitrary write, or demonstrated privilege escalation is shown.
* Privileged kernel/device-management lifetime path: +1. The corruption occurs in trusted media driver registration and async notifier lifetime management.

Paranoid total: 4

Call-site confidence: medium. The patch shows the helper and registration path directly, and the commit explains the notifier lifetime consequence, but full downstream notifier callback use sites are not included.

## 3. Reachability analysis

The issue is local and not network reachable. A practical trigger normally requires control over sensor driver module loading or unloading, which usually means root or CAP_SYS_MODULE. Namespace or container impact is limited in normal deployments because module management is host-level and not delegated to ordinary containers. The affected path is relevant mostly to V4L2 sensor drivers using async subdev registration, especially systems where v4l2-fwnode is built in and sensor drivers are loadable modules.

## 4. Severity interpretation

This behaves more like a borderline Moderate issue requiring manual review than an ordinary low-priority cleanup. The realistic impact is local DoS through stale module or subdevice use after premature module removal. The theoretical risk is higher because module lifetime bugs can become use-after-free or stale callback issues, but the patch does not show controlled reclaim, attacker-controlled replacement, arbitrary write, or a concrete LPE chain. Therefore it is not a strong Important candidate by default.

## 5. One-sentence report phrase

A V4L2 async sensor registration bug can overwrite the sensor subdev owner with the wrong module or NULL, allowing premature sensor module removal while notifier state still references the subdevice and creating a local use after free candidate with likely kernel crash impact.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

This should not be auto-closed because it is a real module lifetime and refcounting bug with a plausible stale callback or use-after-free consequence, even though practical triggering usually requires administrative module lifecycle control.

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

Patch: media: v4l2-fwnode: Fix subdev owner overwritten in v4l2_async_register_subdev_sensor() [ Upstream
Commit: 47ef04cd13d38010b580056a9d8840aaab944841
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=47ef04cd13d38010b580056a9d8840aaab944841

Changed files:
  drivers/media/v4l2-core/v4l2-fwnode.c
  include/media/v4l2-async.h

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=47ef04cd13d38010b580056a9d8840aaab944841

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

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

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

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: 2
  Paranoid ActionableScore: 4

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: MODERATE
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): MODERATE REGULAR

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