{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97910 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97910 is a high-severity memory corruption vulnerability in Linux, published on 25 Sep 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-97910 and fix it if it is affected.\n\nWhat it is: CVE-2026-97910 is a high-severity memory corruption vulnerability in Linux, published on 25 Sep 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-97910 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-97910/ (Markdown: https://insights.sbomify.com/CVE-2026-97910/index.md)","id":"CVE-2026-97910","markdown":"https://insights.sbomify.com/CVE-2026-97910/index.md","name":"CVE-2026-97910","record":{"aliases":["AZL-104736","BELL-CVE-2026-97910","DEBIAN-CVE-2026-97910","GHSA-hmww-phv2-5f63","UBUNTU-CVE-2026-97910"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel audio driver","requires_auth":"low_privilege","summary":"Local attackers can trigger buffer overflows in the Spreadtrum audio driver by setting large fragment sizes, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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: sprd: validate compress buffer sizes against fixed allocations\n\nsprd_platform_compr_open() allocates the stage 0 IRAM buffer (32K data\narea) and the stage 1 DDR buffer (2M data area) with fixed sizes, but\nsprd_platform_compr_copy() derives all copy lengths from the user\ncontrolled runtime-\u003efragment_size and the write() count, never\ncomparing them against the physical buffer sizes. The compress core\nonly checks fragment_size * fragments for an u32 overflow in\nsnd_compress_check_input(), so a local user can configure a logical\nbuffer of up to ~4GB via SNDRV_COMPRESS_SET_PARAMS, far exceeding the\nfixed allocations.\n\nA fragment_size larger than the 32K IRAM data area makes the stage 0\ncopy_from_user() overflow past the IRAM allocation, and a buffer_size\nlarger than the 2M DDR buffer makes the wrapping copy at the end of\nsprd_platform_compr_copy() write fully user controlled data past the\nbuffer. No SNDRV_PCM_TRIGGER_START is needed, a write() in SETUP\nstate reaches the copy callback directly.\n\nReject parameters that do not fit into the fixed buffers in\nset_params(), and fix the advertised max fragment size: 128K never\nfitted into the 32K IRAM buffer. The caps values may have been carried over\nfrom the qdsp6 driver, which allocates its buffers according to the\nadvertised maxima, unlike this driver. With 32K as max fragment size\nthe advertised limits are self-consistent: 32K * 64 = 2M equals the\nDDR buffer size.\n\nDiscovered by Atuin - Automated Vulnerability Discovery Engine.","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: sprd: validate compress buffer sizes against fixed allocations","id":"CVE-2026-97910","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"accel: ethosu: Ensure SRAM region size matches job","id":"CVE-2026-97911"},"packages":[],"prev":{"headline":"ASoC: sti: initialize IRQ lock before requesting IRQ","id":"CVE-2026-97909"},"products":["Linux"],"published":"2026-09-25","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-10-19","vendors":["Linux"]},"summary":"Local attackers can trigger buffer overflows in the Spreadtrum audio driver by setting large fragment sizes, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-97910/"}