* [CVE-2026-98460][IMPORTANT] Bluetooth: hci_sock: reject out-of-range OCF values
@ 2026-10-24 16:28 21% AL-KERNEL
0 siblings, 0 replies; 1+ results
From: AL-KERNEL @ 2026-10-24 16:28 UTC (permalink / raw)
To: kernel-cve
CVE: CVE-2026-98460
Priority: IMPORTANT
AL-KERNEL base severity: IMPORTANT
KPANIC flag: NO
Patch: Bluetooth: hci_sock: reject out-of-range OCF values
Commit: 70b0a27bdde0cb524349c8261202c7c9393cf5e9
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=70b0a27bdde0cb524349c8261202c7c9393cf5e9
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98460
Analysis date: Sat, 24 Oct 2026 12:28:32 -0400
ActionableScore: 5
ActionableScore lower bound: unknown
Actionable bucket: Actionable Moderate / Strong Important candidate requiring manual review
Manual review required: YES
Summary:
An unprivileged raw HCI socket can bypass the command allowlist by using a reserved OCF whose low seven bits alias an allowed command, although downstream controller impact is unresolved.
======================================================================
ABOUT THIS REPORT
======================================================================
The original Linux kernel CVE announcement for CVE-2026-98460 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98460
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: IMPORTANT
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-98460 IMPORTANT https://www.kernelcve.org/list/?q=CVE-2026-98460 CHECK WITH IMPACT FROM ORIG NN MODERATE | AEGIS IMPACT MODERATE_KPANIC AEGIS_AS=1 LEGACY=IMPORTANT RESULT=DIFF INDEPENDENT_LEGACY=IMPORTANT INDEPENDENT_RESULT=DIFF TEMP_KPANIC_MERGE=IMPORTANT_WINS_DISAGREEMENT PRE_MERGE_LEGACY=IMPORTANT (final Legacy and Aegis differ; FINAL: IMPORTANT, Aegis: MODERATE_KPANIC) 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:L/A:H';CWE-863;*CWE-20;CWE-697;Other CVSS 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L';BEST CVSS score: '6.1';DESCR 'The raw HCI socket security filter masked a 10 bit OCF with 127 before checking its allowlist. An unprivileged local process could therefore submit an out of range reserved OCF that aliases an allowed command in the filter while the original opcode is sent to the Bluetooth controller. This is an authorization filter bypass rather than memory corruption. For the CVSS the PR:L value is used because a local user process and access to the HCI socket interface are required, while CAP_NET_RAW is not required for a command that passes the flawed filter. A conforming controller should reject the reserved opcode, so direct impact is controller dependent. The highest grounded concern is unauthorized controller state modification or Bluetooth availability loss on controllers with unexpected or vendor specific handling. There is no evidence of UAF, OOB access, kernel code execution, or direct remote reachability. Automated impact decision path. The original SimpleNet classifier selected MODERATE_KPANIC. The primary LLM estimated paranoid CVSS 6.1 and the production ActionableScore returned 5 with recommendation Actionable Moderate / Strong Important candidate requiring manual review. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. Recorded rule transitions were CVSS and initial triage stage MODERATE_KPANIC to IMPORTANT because the CVSS score, vector or bug class threshold rule was applied. KP and FD specialist checks stage IMPORTANT to IMPORTANT because a specific evidence based protection or manual review veto was applied. final reconciliation stage IMPORTANT to IMPORTANT because KP specialist did not establish a qualifying panic. The legacy KP specialist produced a review artifact and its decision was processed by the applicable KP rules. The legacy FD or DH downgrade specialist produced a review artifact and its decision was processed by the applicable downgrade and preservation rules. Exact triggered rule markers were INCREASED_TO_HIGH_BASED_ON_GUESSCVSS and V59_LEGACY_CLASSA_KP_VETO and MANUAL_REVIEW_REQUIRED and V42_LEGACY_CLASSA_FD_VETO and MANUAL_REVIEW_REQUIRED and TEMP_KPANIC_MERGE_IMPORTANT_WINS and KPANIC_UNSUPPORTED_REMOVED. The independent weaker Aegis shadow evaluated CVSS 2.7 and ActionableScore 1 with primitive class CLASS_C and manual review REQUIRED. Its independently reconciled impact was MODERATE_KPANIC. Cross model aggregation changed the production result under an enabled evidence gated merge rule. The final reported impact is IMPORTANT.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate / Strong Important candidate requiring manual review (with actual score 5) MAYBE REMOTE OOB SIMPLEFIX NETWORK LINUS INCREASED_TO_HIGH_BASED_ON_GUESSCVSS V59_LEGACY_CLASSA_KP_VETO MANUAL_REVIEW_REQUIRED V42_LEGACY_CLASSA_FD_VETO MANUAL_REVIEW_REQUIRED TEMP_KPANIC_MERGE_IMPORTANT_WINS KPANIC_UNSUPPORTED_REMOVED - - checked
======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================
ActionableScore=5
PrimitiveClass=CLASS_A
RealUAF=NO
HostAdminRequired=NO
NamespaceScopedPrivilege=UNKNOWN
ImportantCandidate=YES
ManualReview=REQUIRED
AutoDowngradeAllowed=NO
RequiresHostUID0=NO
AuthorizationDecisionBypass=YES
ProtectedResourceImpact=UNRESOLVED
B4PendingReview=YES
B4PendingConfirmed=NO
1. ActionableScore
* Raw base score: 5.
* Conservative score: 5; no floor or cap applied.
* Raw paranoid score: 5.
* Paranoid score: 5; controller-dependent effects are not additionally scored.
* Final recommended bucket: **Actionable Moderate / Strong Important candidate requiring manual review**::
2. Signal breakdown
* +2 Concrete authorization decision bypass: without `CAP_NET_RAW`, an out-of-range OCF aliases an allowlisted bit and changes the filter result from `-EPERM` to permission to send.
* +2 Strong semantic reinterpretation: authorization checks `ocf & 127`, while the unmasked 10-bit opcode is subsequently sent to the controller. This scores the check/use representation mismatch, distinct from the resulting authorization decision.
* +1 Local unprivileged trigger: the commit explicitly identifies an unprivileged raw HCI socket as able to submit the reserved OCF.
* No memory-corruption, UAF, arbitrary-write, confidentiality, LPE, or kernel-crash points.
* No controller integrity or availability point: conforming controllers reject the opcode, and no particular harmful controller behavior is shown.
3. Reachability analysis
The evidenced actor is a non-UID-0 local process with access to the raw HCI socket. The flawed allowlist itself lets the command pass without `CAP_NET_RAW`, so effective host-administrator privilege is not required. Bluetooth controller availability is a prerequisite, but no unusual hardware or privileged prior setup is established. Namespace capability scope is not resolved and is unnecessary to the proven capability bypass. Actual security impact after transmission depends on controller-specific handling.
4. Primitive and severity reading
The primitive is an authorization-filter bypass caused by checking a truncated opcode while sending the original opcode. It is CLASS_A authorization/semantic confusion, not memory corruption. The DENY-to-ALLOW path in `hci_sock_sendmsg()` is directly shown, and the fix cleanly rejects unrepresentable OCF values.
B4PendingReview is warranted because below-host-admin reachability and the bypass are grounded. B4PendingConfirmed remains NO because no specific reserved opcode, vulnerable controller behavior, or resulting protected-state modification is demonstrated. ImportantCandidate is YES and automatic downgrade is unsafe, but proven impact remains below demonstrated LPE or broad compromise.
5. One-sentence report phrase
An unprivileged raw HCI socket can bypass the command allowlist by using a reserved OCF whose low seven bits alias an allowed command, although downstream controller impact is unresolved.
6. Manual review advice
MANUAL CHECK REQUIRED
Confirm affected-controller handling of reserved opcodes and whether any such opcode changes protected controller state or causes meaningful Bluetooth denial of service.
7. Call-site confidence
Call-site confidence: high
======================================================================
UPSTREAM PATCH SUMMARY
======================================================================
Patch: Bluetooth: hci_sock: reject out-of-range OCF values
Commit: 70b0a27bdde0cb524349c8261202c7c9393cf5e9
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=70b0a27bdde0cb524349c8261202c7c9393cf5e9
Commit description:
The raw HCI socket security filter has 128 OCF bits per supported OGF,
but masks the 10-bit OCF with 127 before looking up the command. An
unprivileged socket can therefore submit a reserved OCF that aliases an
allowlisted command modulo 128.
A conforming controller should reject reserved opcodes. Nevertheless,
the security decision must apply to the opcode that will actually be
sent, especially since controller-specific behavior is outside the host
stack's control.
Reject OCF values that cannot be represented by the security filter
instead of aliasing them onto an unrelated command.
Fixes: 1da177e ("Linux-2.6.12-rc2")
Cc: [email protected]
Signed-off-by: Aldo Ariel Panzardo <[email protected]>
Signed-off-by: Luiz Augusto von Dentz <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Changed files:
net/bluetooth/hci_sock.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=70b0a27bdde0cb524349c8261202c7c9393cf5e9
======================================================================
DETAILED REPORT METHODOLOGY
======================================================================
The original Linux kernel CVE announcement for CVE-2026-98460 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98460
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:L/UI:N/S:U/C:N/I:L/A:L
The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
The Best / paranoid CVSS score: 6.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: 5
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: IMPORTANT
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): IMPORTANT
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 [email protected] (and both
send reply to CVE record itself too and see "reply" button below for howto reply).
^ permalink raw reply [relevance 21%]
Results 1-1 of 1 | reverse | sort options + mbox downloads above
-- links below jump to the message on this page --
2026-10-24 16:28 21% [CVE-2026-98460][IMPORTANT] Bluetooth: hci_sock: reject out-of-range OCF values AL-KERNEL
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox