From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-64549][MODERATE REGULAR] Bluetooth: bpa10x: avoid OOB read of revision string in bpa10x_setup() [ Upstream Date: Sun, 02 Aug 2026 09:03:57 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-64549 X-AL-KERNEL-Priority: MODERATE REGULAR X-AL-KERNEL-Severity: MODERATE REGULAR X-AL-KERNEL-Base-Severity: MODERATE X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 2 X-AL-KERNEL-ActionableScore-Lower: 0 X-AL-KERNEL-Commit: 1813add71e386f77b3040e6c8dc9b7b3ff965a6c List-Id: CVE: CVE-2026-64549 Priority: MODERATE REGULAR AL-KERNEL base severity: MODERATE KPANIC flag: NO Patch: Bluetooth: bpa10x: avoid OOB read of revision string in bpa10x_setup() [ Upstream Commit: 1813add71e386f77b3040e6c8dc9b7b3ff965a6c Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1813add71e386f77b3040e6c8dc9b7b3ff965a6c Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64549 Analysis date: Sun, 02 Aug 2026 09:03:57 -0400 ActionableScore: 2 ActionableScore lower bound: 0 Actionable bucket: Ordinary Moderate / Low-like but manual disclosure review recommended Manual review required: NO Summary: A device-controlled OOB read in the Bluetooth bpa10x setup path can disclose adjacent slab memory through the kernel log or firmware-info debugfs when a malicious or faulty adapter returns a short or unterminated revision response. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-64549 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64549 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-64549 MODERATE CHECK WITH IMPACT FROM ORIG NN IMPORTANT Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L';CWE-126;CWE-125;*CWE-200;Other CVSS 'AV:P/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N';BEST CVSS score: '5.2';DESCR 'An OOB read in the Bluetooth/USB bpa10x setup path occurs because the device controlled revision response is passed to string printing without a validated length or NUL terminator. A malicious or faulty bpa10x compatible device can return a one byte status only response or an unterminated payload, causing the kernel to read adjacent slab bytes and place them in the kernel log and the firmware info debugfs file. For the CVSS the PR:N is used in the paranoid score because the triggering input is supplied by the attached device and does not require an authenticated user on the target. The issue is not network reachable and normally requires physical access or a supply chain style malicious USB Bluetooth adapter. Impact is primarily information disclosure of adjacent kernel memory, with low availability risk if the unbounded read causes a fault or excessive log activity.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like but manual disclosure review recommended (with actual score 1) MAYBE WRITE OOB SIMPLEFIX SKB HARDWARE DEBUGFS LOWERED_FROM_HIGH_BASED_ON_GUESSCVSS DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5 - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=2 ActionableScoreLower=0 ## 1. ActionableScore * Conservative score: 0 * Paranoid score: 2 * Final recommended bucket: **Ordinary Moderate / Low-like but manual disclosure review recommended**:: ## 2. Signal breakdown Paranoid scoring: * Firmware-mediated external influence: +1 The revision string is controlled by the attached Bluetooth USB device or its firmware. * Confidentiality impact plausible: +1 The unbounded `%s` read can copy adjacent slab memory into the kernel log and firmware-info debugfs file. * Physical-only or rare hardware-only condition: not subtracted in paranoid score For the paranoid score, the malicious-device or supply-chain scenario is treated as the relevant exposure model. * No remote/network trigger: +0 The path is not reachable over Bluetooth radio traffic or normal network input. * No generic memory corruption: +0 This is an OOB read, not OOB write, UAF, double-free, type confusion, or refcount corruption. * No LPE signal: +0 The patch does not show write capability, callback control, reclaim, or object replacement. * Availability: +0 A crash is possible in theory from an unbounded read, but the demonstrated impact is disclosure to logs/debugfs, not reliable DoS. Conservative scoring: * Firmware-mediated external influence: +1 * Confidentiality impact plausible: +1 * Physical-only or rare hardware-only condition: -2 Reliable triggering normally requires a malicious or faulty bpa10x-compatible physical USB Bluetooth adapter. Conservative total: 0. Paranoid total: 2. ## 3. Reachability analysis The bug is triggered during `bpa10x_setup()` when the driver queries revision information from the device. A malicious or malformed device can return a one-byte status-only response or a non-NUL-terminated payload, causing the kernel to read beyond the received skb data. This is not remotely network-triggerable. It normally requires physical access, malicious hardware, compromised firmware, or a supply-chain scenario involving a compatible Bluetooth USB device. Namespaces and containers do not materially lower the privilege requirement because the trigger is device controlled during driver setup, not a normal unprivileged local API. The affected device path is hardware-specific and not broad/default exposure. Call-site confidence: high. The patch directly shows the vulnerable `%s` consumers and the bounded `%.*s` replacement. ## 4. Severity interpretation This behaves more like a Low-like or ordinary Moderate information disclosure issue than an Important-class kernel vulnerability. The theoretical primitive is a kernel OOB read from adjacent slab memory, and the disclosure sink is concrete because bytes can reach the kernel log and firmware-info debugfs file. However, exploitation is constrained by physical or firmware-mediated device control, and there is no evidence of write corruption, privilege escalation, or remote reachability. The issue should not be treated as generic memory corruption or LPE. It is primarily a device-mediated kernel memory disclosure with limited practical exposure. ## 5. One-sentence report phrase A device-controlled OOB read in the Bluetooth bpa10x setup path can disclose adjacent slab memory through the kernel log or firmware-info debugfs when a malicious or faulty adapter returns a short or unterminated revision response. ## 6. Manual review recommendation MANUAL CHECK RECOMMENDED Manual review is recommended because this is a concrete kernel memory disclosure path, even though practical exploitation is constrained by physical or firmware-mediated access and does not show privilege escalation. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: Bluetooth: bpa10x: avoid OOB read of revision string in bpa10x_setup() [ Upstream Commit: 1813add71e386f77b3040e6c8dc9b7b3ff965a6c Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1813add71e386f77b3040e6c8dc9b7b3ff965a6c Changed files: drivers/bluetooth/bpa10x.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=1813add71e386f77b3040e6c8dc9b7b3ff965a6c ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-64549 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64549 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:P/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N The Best / paranoid CVSS vector: AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L 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: 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).