This vulnerability in the Qualcomm audio stack exposes a dangerous pattern: developers apply guards to 'enable' operations (perceived as risky because they allocate state) while leaving 'disable' paths unprotected under the assumption that cleanup is inherently safe. The bug exists because .info is allocated lazily on first enable, creating two distinct NULL states for the disable handler to navigate — 'never allocated' and 'allocated but with invalid index' — but the disable path was never updated when lazy allocation was introduced. The result is two different failure modes with wildly different blast profiles. The 'never enabled' path triggers a kernel oops — loud and crashy. The 'enabled once, wrong interface on disable' path triggers a silent out-of-bounds 4-byte write that clears pipe fields without crashing. The latter is your exploit path: no crash means the system keeps running while kernel slab state is quietly corrupted. The AF_QIPCRTR unprivileged local access vector means this is reachable from userspace without privileges, compounding the risk. The one-line fix (adding the same NULL guard that exists on enable) is deceptively simple — its simplicity is evidence of how invisible the asymmetry was, not evidence that it should have been caught. The real vulnerability isn't the missing check; it's the architectural assumption that disable operations don't require equivalent rigor. Treat paired operations like enable/disable as a single security contract. When one side gains a new invariant (like lazy allocation), audit the inverse path immediately. The existence of a guard on one branch should be treated as a flag that the other branch needs equivalent scrutiny, not as evidence that the pair has been reviewed.
CVE-2026-72446
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: qcom: reject stream disable with no active interface handle_uaudio_stream_req() resolves an interface index with info_idx_from_ifnum(), which returns -EINVAL when no interface matches. The enable branch and the response: cleanup label both guard against a negative index, but the disable branch does not: it forms info = &uadev[pcm_card_num].info[info_idx] and dereferences it. uadev[].info is a pointer allocated only when a stream is first enabled, so a negative info_idx on the disable path is unsafe in two ways: - If the card was never enabled, .info is NULL and &info[-EINVAL] is a wild pointer; reading info->data_ep_pipe faults (kernel oops). - If the card was enabled at least once (.info allocated) and the disable names an interface that does not match, &info[-EINVAL] points before the allocation; info->data_ep_pipe / info->sync_ep_pipe are an out-of-bounds slab read and, when non-zero, an out-of-bounds 4-byte write (both pipe fields are cleared to 0). That is memory corruption, not just a NULL dereference. The request is reachable from unprivileged local userspace over AF_QIPCRTR. Reject a disable request with no resolved interface, matching the guard the enable path already has.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisA detailed technical summary for this CVE is being prepared.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataThere is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $4,900. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-72446 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesThis vulnerability in the Qualcomm audio stack exposes a dangerous pattern: developers apply guards to 'enable' operations (perceived as risky because they allocate state) while leaving 'disable' paths unprotected under the assumption that cleanup is inherently safe. The bug exists because `.info` is allocated lazily on first enable, creating two distinct NULL states for the disable handler to navigate — 'never allocated' and 'allocated but with invalid index' — but the disable path was never updated when lazy allocation was introduced. The result is two different failure modes with wildly different blast profiles. The 'never enabled' path triggers a kernel oops — loud and crashy. The 'enabled once, wrong interface on disable' path triggers a silent out-of-bounds 4-byte write that clears pipe fields without crashing. The latter is your exploit path: no crash means the system keeps running while kernel slab state is quietly corrupted. The AF_QIPCRTR unprivileged local access vector means this is reachable from userspace without privileges, compounding the risk. The one-line fix (adding the same NULL guard that exists on enable) is deceptively simple — its simplicity is evidence of how invisible the asymmetry was, not evidence that it should have been caught. The real vulnerability isn't the missing check; it's the architectural assumption that disable operations don't require equivalent rigor. Treat paired operations like enable/disable as a single security contract. When one side gains a new invariant (like lazy allocation), audit the inverse path immediately. The existence of a guard on one branch should be treated as a flag that the other branch needs equivalent scrutiny, not as evidence that the pair has been reviewed.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-72446 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data