{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72446 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72446 is a high-severity vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-72446 and fix it if it is affected.\n\nWhat it is: CVE-2026-72446 is a high-severity vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-72446 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-72446/ (Markdown: https://insights.sbomify.com/CVE-2026-72446/index.md)","id":"CVE-2026-72446","markdown":"https://insights.sbomify.com/CVE-2026-72446/index.md","name":"CVE-2026-72446","record":{"aliases":["BELL-CVE-2026-72446","DEBIAN-CVE-2026-72446","GHSA-xg4f-mwxf-g67f","UBUNTU-CVE-2026-72446"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel ALSA","requires_auth":"low_privilege","summary":"A local attacker can trigger a kernel crash or memory corruption by sending a malformed USB audio stream disable request via AF_QIPCRTR.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nALSA: usb-audio: qcom: reject stream disable with no active interface\n\nhandle_uaudio_stream_req() resolves an interface index with\ninfo_idx_from_ifnum(), which returns -EINVAL when no interface matches.\nThe enable branch and the response: cleanup label both guard against a\nnegative index, but the disable branch does not: it forms\ninfo = \u0026uadev[pcm_card_num].info[info_idx] and dereferences it.\n\nuadev[].info is a pointer allocated only when a stream is first enabled,\nso a negative info_idx on the disable path is unsafe in two ways:\n\n - If the card was never enabled, .info is NULL and \u0026info[-EINVAL] is a\n   wild pointer; reading info-\u003edata_ep_pipe faults (kernel oops).\n\n - If the card was enabled at least once (.info allocated) and the\n   disable names an interface that does not match, \u0026info[-EINVAL] points\n   before the allocation; info-\u003edata_ep_pipe / info-\u003esync_ep_pipe are an\n   out-of-bounds slab read and, when non-zero, an out-of-bounds 4-byte\n   write (both pipe fields are cleared to 0). That is memory corruption,\n   not just a NULL dereference.\n\nThe request is reachable from unprivileged local userspace over\nAF_QIPCRTR. Reject a disable request with no resolved interface, matching\nthe guard the enable path already has.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"ALSA: usb-audio: qcom: reject stream disable with no active interface","id":"CVE-2026-72446","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"sctp: hold socket lock when dumping endpoints in sctp_diag","id":"CVE-2026-72447"},"packages":[],"prev":{"headline":"ALSA: usb-audio: qcom: clear opened when stream enable fails","id":"CVE-2026-72445"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"A local attacker can trigger a kernel crash or memory corruption by sending a malformed USB audio stream disable request via AF_QIPCRTR.","url":"https://insights.sbomify.com/CVE-2026-72446/"}