[CVE-2026-74304][LOW] Bluetooth: hci_qca: fix NULL pointer dereference in qca_setup() for non-serdev device [ Upstream

[CVE-2026-74304][LOW] Bluetooth: hci_qca: fix NULL pointer dereference in qca_setup() for non-serdev device [ Upstream

[AL-KERNEL]

CVE: CVE-2026-74304
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: Bluetooth: hci_qca: fix NULL pointer dereference in qca_setup() for non-serdev device [ Upstream
Commit: 0704c04769ccc1a0939682db35d816dfa5fe75dc
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0704c04769ccc1a0939682db35d816dfa5fe75dc
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74304
Analysis date: Sat, 15 Aug 2026 23:22:28 -0400
ActionableScore: 2
ActionableScore lower bound: 0
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-74304 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74304

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-74304	LOW	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H';**CWE-476;CWE-703;CWE-754;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.5';DESCR 'A NULL pointer dereference in the Bluetooth hci_qca setup path can occur because qca_setup() used hu serdev and qcadev fields even when the HCI UART device was attached through a non serdev path. This can crash the kernel or break Bluetooth controller initialization during local device setup. For the CVSS the PR:L paranoid interpretation covers environments where a local non-root user or service account can access a UART device or delegated Bluetooth setup path, while typical host configuration usually requires administrator privileges. The issue is not network reachable and cannot normally be triggered by a remote Bluetooth peer because it occurs during the local driver setup path. Impact is denial of service only via NULL pointer dereference, with no evidence of UAF, OOB access, information disclosure, or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1)  SKIP CVE-2026-74304 UNKNOWN SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	NULLPTR SIMPLEFIX HARDWARE  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	-	-	checked

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

ActionableScore=2
ActionableScoreLower=0

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

2. Signal breakdown
* Reliable kernel crash / strong DoS: +1. The patch fixes a direct NULL pointer dereference in `qca_setup()` when `hu->serdev` is NULL for non-serdev HCI UART attachment paths.
* Local unprivileged trigger: +1 only in the paranoid interpretation. This applies only if a local non-root user or reduced-privilege service can access a UART or delegated Bluetooth setup path.
* Requires admin/root/CAP_* in typical deployments: -2 for the conservative score. Binding or initializing this Bluetooth UART driver path normally requires administrator-level device control.
* No memory corruption bonus. This is a NULL dereference, not UAF, OOB write, double free, refcount corruption, object reuse, or type confusion.
* No LPE bonus. The patch does not show attacker-controlled reclaim, writable stale object access, callback control, arbitrary write, or a privilege boundary bypass.
* No confidentiality or integrity impact. The plausible effect is setup failure or kernel crash only.

3. Reachability analysis
The bug is triggered during local Bluetooth controller setup for Qualcomm HCI UART devices attached through non-serdev paths. It is not reachable from a remote Bluetooth peer or over the network because the vulnerable dereference happens in the local driver setup path before normal peer-driven Bluetooth protocol handling. In typical deployments, triggering requires root or equivalent device-management privileges. A paranoid PR:L interpretation is possible only for systems that delegate UART or Bluetooth setup operations to a local service account, container, or non-root user. The affected path is hardware and configuration dependent, not a broad default kernel attack surface. Call-site confidence: high, because the vulnerable dereferences and fixed checks are visible in the supplied patch.

4. Severity interpretation
This behaves like an ordinary Moderate or Low-like local DoS issue. The theoretical impact is a kernel NULL pointer dereference during device setup. Realistic exploitation evidence supports crash or failed Bluetooth initialization, not privilege escalation. There is no demonstrated memory corruption primitive beyond invalid NULL dereference, and no remote reachability.

5. One-sentence report phrase
A NULL pointer dereference in the Bluetooth hci_qca setup path can crash the kernel when a non-serdev HCI UART device reaches qca_setup(), but typical triggering requires local device-management privileges and no privilege escalation or network attack path is indicated.

6. Manual review recommendation
NO MANUAL CHECK NEEDED
This can be auto-closed for urgent triage purposes because it is a local setup-time NULL dereference with DoS-only impact, typical admin-level reachability, and no supported memory corruption or privilege-escalation primitive.

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

Patch: Bluetooth: hci_qca: fix NULL pointer dereference in qca_setup() for non-serdev device [ Upstream
Commit: 0704c04769ccc1a0939682db35d816dfa5fe75dc
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0704c04769ccc1a0939682db35d816dfa5fe75dc

Changed files:
  drivers/bluetooth/hci_qca.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=0704c04769ccc1a0939682db35d816dfa5fe75dc

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

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

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

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