{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72304 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72304 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-72304 and fix it if it is affected.\n\nWhat it is: CVE-2026-72304 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-72304 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-72304/ (Markdown: https://insights.sbomify.com/CVE-2026-72304/index.md)","id":"CVE-2026-72304","markdown":"https://insights.sbomify.com/CVE-2026-72304/index.md","name":"CVE-2026-72304","record":{"aliases":["BELL-CVE-2026-72304","DEBIAN-CVE-2026-72304","GHSA-p327-qw84-66rm","UBUNTU-CVE-2026-72304"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A time-of-check time-of-use race condition in the Linux kernel's SOF IPC4 control allows attackers to read stale data or corrupt memory via crafted audio control operations.","user_interaction":"not_required","vuln_class":"race_condition"},"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\nASoC: SOF: ipc4-control: Fix TOCTOU in sof_ipc4_bytes_put\n\nIn sof_ipc4_bytes_put(), the copy size is derived from the old\ndata-\u003esize in the buffer rather than the incoming new data's size\nfield from ucontrol. If the new data has a different size, the copy\nuses the wrong length: it may truncate valid data or copy stale bytes.\n\nFix by validating and using the incoming data's sof_abi_hdr.size from\nucontrol before copying.","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":"ASoC: SOF: ipc4-control: Fix TOCTOU in sof_ipc4_bytes_put","id":"CVE-2026-72304","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"VDUSE: avoid leaking information to userspace","id":"CVE-2026-72305"},"packages":[],"prev":{"headline":"ASoC: SOF: ipc4-control: Validate notification payload size","id":"CVE-2026-72303"},"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["Linux"]},"summary":"A time-of-check time-of-use race condition in the Linux kernel's SOF IPC4 control allows attackers to read stale data or corrupt memory via crafted audio control operations.","url":"https://insights.sbomify.com/CVE-2026-72304/"}