From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-72445][LOW] ALSA: usb-audio: qcom: clear opened when stream enable fails [ Upstream Date: Sun, 16 Aug 2026 07:43:00 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-72445 X-AL-KERNEL-Priority: LOW X-AL-KERNEL-Severity: LOW X-AL-KERNEL-Base-Severity: LOW X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 2 X-AL-KERNEL-ActionableScore-Lower: 1 X-AL-KERNEL-Commit: 53c23d56b46b1ae51574d92110895086aead7ad7 List-Id: CVE: CVE-2026-72445 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: ALSA: usb-audio: qcom: clear opened when stream enable fails [ Upstream Commit: 53c23d56b46b1ae51574d92110895086aead7ad7 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=53c23d56b46b1ae51574d92110895086aead7ad7 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72445 Analysis date: Sun, 16 Aug 2026 07:43:00 -0400 ActionableScore: 2 ActionableScore lower bound: 1 Actionable bucket: Ordinary Moderate / Low-like Manual review required: NO Summary: A state cleanup bug in the ALSA qcom USB audio offload enable error path can leave a substream marked opened after invalid service_interval validation, causing a limited local audio DoS until disable or disconnect. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-72445 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72445 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-72445 LOW CHECK WITH IMPACT FROM ORIG NN LOW 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:L';CWE-703;CWE-754;CWE-404;BEST CVSS score: '3.3';DESCR 'A state cleanup bug in the ALSA qcom USB audio offload path can leave subs opened set after stream enable fails due to an invalid service_interval. The affected substream can then remain wedged and return EBUSY until a later disable or disconnect, causing a limited audio denial of service. For the CVSS the PR:L is selected because reliable triggering normally requires a local user or local audio service context able to start or influence the USB audio offload stream. The issue is not network reachable and does not indicate memory corruption, information disclosure, or privilege escalation. Impact is limited availability loss for the audio stream rather than a kernel crash.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 2) SKIP CVE-2026-72445 UNKNOWN SKIP No affected files built, so skip this CVE NO - - unknown MAYBE USB SIMPLEFIX ERRORPATH HARDWARE LINUS - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=2 ActionableScoreLower=1 ## 1. ActionableScore * Conservative score: 1 * Paranoid score: 2 * Final recommended bucket: **Ordinary Moderate / Low-like** ## 2. Signal breakdown Conservative signals: * Local unprivileged trigger: +1. A local user or local audio service context may be able to initiate the affected USB audio offload stream path. * Availability impact realistic: +1. The substream can become wedged and return EBUSY until disable or disconnect. * Rare AND difficult-to-reach subsystem/configuration: -1. This is specific to Qualcomm USB audio offload support, not a broad ALSA core path. Paranoid additional signal: * Firmware-mediated external influence: +1. The invalid service_interval comes through the qcom USB audio offload request path, so a device or firmware mediated request may influence the bad state, but this is not remote network reachability. No memory corruption signals apply. No UAF, OOB access, double free, refcount misuse, stale callback, arbitrary write, or kernel crash is indicated by the patch. ## 3. Reachability analysis The bug is reachable through the ALSA qcom USB audio offload stream request handling path. Realistic triggering requires a local audio user, an audio service, or a device or firmware path capable of producing an enable request with an invalid service_interval. Namespaces do not materially improve reachability unless the audio device is explicitly delegated into a container. The affected path is hardware and feature specific, so exposure is narrower than generic ALSA or USB audio code. Call-site confidence: high, because the patch directly shows the failing state transition and the corrected error path in handle_uaudio_stream_req(). ## 4. Severity interpretation This behaves like a low impact local denial of service, not an actionable Moderate or Important-class vulnerability. The failure mode is a stale opened state bit that wedges one substream with EBUSY until cleanup, disable, or disconnect. There is no demonstrated memory corruption, privilege escalation, information disclosure, cross-boundary access, or system-wide crash. ## 5. One-sentence report phrase A state cleanup bug in the ALSA qcom USB audio offload enable error path can leave a substream marked opened after invalid service_interval validation, causing a limited local audio DoS until disable or disconnect. ## 6. Manual review recommendation NO MANUAL CHECK NEEDED This can be auto-closed for urgent security triage because the patch supports only a limited availability issue in a device-specific audio offload path, with no memory corruption or privilege boundary bypass. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: ALSA: usb-audio: qcom: clear opened when stream enable fails [ Upstream Commit: 53c23d56b46b1ae51574d92110895086aead7ad7 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=53c23d56b46b1ae51574d92110895086aead7ad7 Changed files: sound/usb/qcom/qc_audio_offload.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=53c23d56b46b1ae51574d92110895086aead7ad7 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-72445 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72445 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: Not available The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L The Best / paranoid CVSS score: 3.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: 1 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).