[CVE-2026-80677][MODERATE REGULAR] driver core: use READ_ONCE() for dev->driver in dev_has_sync_state() [ Upstream

[CVE-2026-80677][MODERATE REGULAR] driver core: use READ_ONCE() for dev->driver in dev_has_sync_state() [ Upstream

[AL-KERNEL]

CVE: CVE-2026-80677
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: driver core: use READ_ONCE() for dev->driver in dev_has_sync_state() [ Upstream
Commit: 89789e4c141904506163dcb91c7289a074573931
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=89789e4c141904506163dcb91c7289a074573931
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80677
Analysis date: Fri, 28 Aug 2026 06:53:48 -0400
ActionableScore: 2
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like with manual review recommended
Manual review required: YES

Summary:
No one-sentence report phrase was found.

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

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

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-80677	MODERATE	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';CWE-362;**CWE-476;CWE-667;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'dev_has_sync_state can read dev driver twice without device_lock, first for the NULL check and then for dereferencing sync_state. A concurrent device unbind can clear dev driver between these reads, allowing the second read to become NULL and causing a kernel crash. For the CVSS the PR:L is used only for the paranoid score because some environments may delegate limited device or driver control to a local service account, but typical reliable triggering requires administrator level driver unbind control. The issue is not network reachable and is triggered through local driver core state changes. Impact is denial of service via NULL pointer dereference, with no concrete evidence of information disclosure or privilege escalation.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like with manual review recommended (with actual score 1)  SKIP CVE-2026-80677 UNKNOWN SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	DANGER SIMPLEFIX HARDWARE LINUS  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH	-	-	checked

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

ActionableScore=2
ActionableScoreLower=0

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

2. Signal breakdown
* Reliable kernel crash / strong DoS: +1. The race can make the second dev->driver read return NULL and then dereference drv->sync_state, causing an Oops or panic.
* Broad/default/common subsystem: +1. The bug is in driver core, although the reachable trigger path is device-management oriented.
* Hard or unreliable race / special timing required: -1. Triggering requires a concurrent dev_has_sync_state() caller and device unbind window.
* Requires admin/root/CAP_* in typical deployments: -2 for the conservative score. Reliable unbind or driver management normally requires administrator-level control.
* Paranoid privilege interpretation: no -2 penalty and local low-privilege relevance considered only where device control is delegated to a service account, container root, or reduced-capability management process.
* No generic memory corruption signal. The patch supports a double-read race and NULL dereference, not UAF, stale object reuse, overwrite, type confusion, or refcount takeover.
* No confidentiality or integrity signal. There is no supported read-back, disclosure, write primitive, or privilege-escalation path.

3. Reachability analysis
The realistic trigger is local and tied to driver/device management state changes, especially concurrent unbind while dev_has_sync_state() runs without device_lock(). In normal deployments this is admin-controlled, so conservative reachability is privileged local. Namespaces or service delegation may lower the practical privilege boundary if a reduced-capability process can initiate relevant device unbind or driver-core operations. The path is not network reachable.

4. Severity interpretation
This behaves like an ordinary Moderate or Low-like DoS issue, not an Important-class vulnerability. The theoretical risk is a driver-core race on a shared pointer, but the demonstrated primitive is a NULL pointer dereference only. There is no evidence from the patch of UAF reclaim, controlled object replacement, writable stale access, callback control, or LPE.

5. One-sentence report phrase
A race in dev_has_sync_state() can read dev->driver twice without device_lock(), allowing concurrent unbind to clear the pointer between the NULL check and sync_state dereference and causing a local privileged kernel crash.

6. Manual review recommendation
MANUAL CHECK RECOMMENDED. YES REQUIRES MANUAL CHECK because this is a driver-core race in a common subsystem, but current evidence points to DoS only and does not justify Important severity.

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

Patch: driver core: use READ_ONCE() for dev->driver in dev_has_sync_state() [ Upstream
Commit: 89789e4c141904506163dcb91c7289a074573931
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=89789e4c141904506163dcb91c7289a074573931

Changed files:
  include/linux/device.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=89789e4c141904506163dcb91c7289a074573931

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

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

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

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

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