[CVE-2026-74303][MODERATE REGULAR] Bluetooth: hci_qca: fix NULL pointer dereference in qca_dmp_hdr() for non-serdev device [ Upstream

[CVE-2026-74303][MODERATE REGULAR] Bluetooth: hci_qca: fix NULL pointer dereference in qca_dmp_hdr() for non-serdev device [ Upstream

[AL-KERNEL]

CVE: CVE-2026-74303
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: Bluetooth: hci_qca: fix NULL pointer dereference in qca_dmp_hdr() for non-serdev device [ Upstream
Commit: 809230cc25dde1d6bb00de2a1eeb5f3199402fbe
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=809230cc25dde1d6bb00de2a1eeb5f3199402fbe
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74303
Analysis date: Sat, 15 Aug 2026 14:20:08 -0400
ActionableScore: 2
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like, not an Important candidate
Manual review required: NO

Summary:
A NULL pointer dereference in Bluetooth hci_qca devcoredump handling can crash the kernel on non-serdev hci_uart QCA devices when `qca_dmp_hdr()` dereferences `hu->serdev`, with no evidence of privilege escalation or data exposure.

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

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

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: NO

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

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

CVE-2026-74303	MODERATE	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:A/AC:H/PR:N/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:H';BEST CVSS score: '5.3';DESCR 'A NULL pointer dereference can occur in the Bluetooth hci_qca devcoredump header path because qca_dmp_hdr() dereferences hu serdev even for hci_uart devices attached through non-serdev paths where that pointer is NULL. The immediate impact is a kernel crash or warning when a Qualcomm controller dump is collected for such a device. For the CVSS the PR:N is used in the paranoid score because a nearby attacker may not need local privileges if a Bluetooth adjacent trigger can force the controller into the devcoredump path, but this requires confirmation. The issue is not Internet reachable, but it may be adjacent network reachable through Bluetooth radio proximity in affected hardware setups. Impact is denial of service only because the patch shows a NULL dereference and no evidence of UAF, OOB access, information disclosure, or privilege escalation.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like, not an Important candidate (with actual score 1)  SKIP CVE-2026-74303 UNKNOWN SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	NULLPTR SIMPLEFIX HARDWARE DEBUGFS  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH	-	-	guess

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

ActionableScore=2
ActionableScoreLower=0

## 1. ActionableScore

* Conservative score: 0
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate / Low-like, not an Important candidate**

## 2. Signal breakdown

Conservative scoring:

* Reliable kernel crash / strong DoS: +1. The patch fixes a direct NULL pointer dereference in `qca_dmp_hdr()` when `hu->serdev` is NULL.
* Requires admin/root/CAP in typical deployments: -2. The conservative trigger model requires control over hci_uart setup or a local privileged path that reaches Qualcomm devcoredump handling.
* Rare AND difficult-to-reach subsystem/configuration: -1. The affected case is specific to Qualcomm Bluetooth hci_qca devices attached through non-serdev paths and requires the devcoredump path.
* Floor applied: 0.

Paranoid scoring:

* Firmware-mediated external influence: +1. A Bluetooth controller failure or firmware/device event may cause the devcoredump path to run, though the patch does not prove a direct radio-triggered path.
* Reliable kernel crash / strong DoS: +1. If the affected path is reached, the NULL dereference is straightforward and can crash the kernel.
* No generic memory corruption: +0. This is a NULL pointer dereference, not UAF, OOB write, double free, type confusion, or refcount corruption.
* No privilege escalation plausible: +0. There is no supported reclaim, overwrite, stale callback, object replacement, or attacker-controlled reuse primitive.
* No confidentiality or integrity impact: +0. The patch shows crash prevention only.

## 3. Reachability analysis

The conservative trigger requires a local privileged actor or system configuration that uses hci_uart with the Qualcomm QCA driver through a non-serdev path and then reaches the devcoredump header generation path. In normal deployments, creating or configuring this device path is not available to an unprivileged local user.

The paranoid interpretation considers Bluetooth-adjacent influence: a nearby attacker might be able to induce controller failure or abnormal firmware behavior that causes a devcoredump. This is not demonstrated by the patch, so it is scored as firmware-mediated external influence rather than fully remote or reliably network-triggerable exposure.

Namespaces and containers do not obviously lower the privilege requirement unless the container is delegated real Bluetooth device control. The path is hardware and driver specific, not a broad default kernel data path.

## 4. Severity interpretation

This behaves like an ordinary Moderate / Low-like kernel DoS issue. The theoretical impact is a kernel crash if the vulnerable devcoredump path is reached on an affected non-serdev QCA Bluetooth setup. Realistic exploitation evidence is limited because the patch only shows a NULL dereference and does not show memory corruption beyond invalid pointer dereference, privilege escalation, information disclosure, or a reliable unprivileged trigger.

The paranoid score is higher only because Bluetooth hardware and firmware events may be externally influenced, but this remains DoS-only and does not reach Actionable Moderate or Important-class handling.

## 5. One-sentence report phrase

A NULL pointer dereference in Bluetooth hci_qca devcoredump handling can crash the kernel on non-serdev hci_uart QCA devices when `qca_dmp_hdr()` dereferences `hu->serdev`, with no evidence of privilege escalation or data exposure.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Manual review is recommended only to confirm whether the devcoredump path can be triggered by a nearby Bluetooth attacker on affected hardware. If no adjacent or unprivileged trigger exists, this can be treated as a low-priority privileged/local DoS.

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

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

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=809230cc25dde1d6bb00de2a1eeb5f3199402fbe

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

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

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

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