PatchSiren cyber security CVE debrief
CVE-2026-72445 Linux CVE debrief
The Linux kernel has a vulnerability in the ALSA usb-audio qcom driver. When enabling a stream, the subs->opened flag is set before validating the service interval. If the interval is invalid, the function jumps to the response label without clearing the flag, causing the substream to be stuck at -EBUSY until it is disabled or disconnected. To address this issue, the subs->opened flag should be cleared on the enable error path.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-15
- Original CVE updated
- 2026-08-15
- Advisory published
- 2026-08-15
- Advisory updated
- 2026-08-15
Who should care
Linux system administrators and users who utilize the ALSA usb-audio qcom driver should be aware of this vulnerability and take necessary steps to verify and mitigate it. This includes reviewing the service interval validation, monitoring for disable or disconnect events, and ensuring that the fix is applied. Additionally, security teams and vulnerability management teams should be aware of this vulnerability and track its status to ensure that it is properly addressed.
Technical summary
The vulnerability is caused by the subs->opened flag being set before validating the service interval in the ALSA usb-audio qcom driver. If the interval is invalid, the function jumps to the response label without clearing the flag, causing the substream to be stuck at -EBUSY. To fix this issue, the subs->opened flag should be cleared on the enable error path. This can be achieved by adding a line to clear the flag in the error handling code.
Defensive priority
Medium
Recommended defensive actions
- Inventory Linux systems using the ALSA usb-audio qcom driver
- Verify service interval validation in the ALSA usb-audio qcom driver
- Monitor for disable or disconnect events to resolve -EBUSY errors
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
Evidence notes
The CVE record and NVD detail provide information about the vulnerability. However, the source detail is thin, and further verification is needed to confirm the affected scope and vendor remediation. Linux system administrators should verify the service interval validation in the ALSA usb-audio qcom driver and monitor for disable or disconnect events to resolve -EBUSY errors. The vulnerability has been resolved in the Linux kernel, but it is essential to ensure that the fix is applied and that the system is properly configured to prevent similar issues.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-72445 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-72445
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-72445 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-72445
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/3c7af07943b2718087ae791cad450af5cf646d90
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/53c23d56b46b1ae51574d92110895086aead7ad7
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/ec6fb1ecada8ddfc3d0e1728e4792d16ae55dcdb
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.