{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93039 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93039 is a high-severity use after free vulnerability in Linux, published on 17 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-93039 and fix it if it is affected.\n\nWhat it is: CVE-2026-93039 is a high-severity use after free vulnerability in Linux, published on 17 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-93039 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-93039/ (Markdown: https://insights.sbomify.com/CVE-2026-93039/index.md)","id":"CVE-2026-93039","markdown":"https://insights.sbomify.com/CVE-2026-93039/index.md","name":"CVE-2026-93039","record":{"aliases":["AZL-102126","BELL-CVE-2026-93039","DEBIAN-CVE-2026-93039","GHSA-w65f-8rhv-gqvr","UBUNTU-CVE-2026-93039"],"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":"none","summary":"A use-after-free vulnerability in the Linux kernel's Meson audio driver allows attackers to potentially execute code or escalate privileges via a double free error during memory reallocation failures.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/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: meson: Keep link pointers valid on realloc failure\n\nmeson_card_reallocate_links() grows the DAI link and private data\narrays with two consecutive krealloc() calls and updates the owner\npointers only after both calls have succeeded.\n\nA successful krealloc() may move the data: it frees the old block and\nreturns a new one. When that happens for the link array and the second\nkrealloc() then fails, card-\u003edai_link still points to the block that\nkrealloc() already freed, and the error path frees the new block too.\nThe probe error path then calls meson_card_clean_references(), which\ndereferences card-\u003edai_link and kfree()s it again, resulting in a\nuse-after-free and a double free.\n\nCommit card-\u003edai_link and card-\u003enum_links right after the first\nkrealloc() succeeds, so the pointer always refers to a valid allocation\nthat meson_card_clean_references() can walk and free. krealloc() with\n__GFP_ZERO zero-initializes the added entries, so walking them on the\nerror path is safe. With both failure paths reduced to a plain return,\ndrop the goto labels and the error message.","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: meson: Keep link pointers valid on realloc failure","id":"CVE-2026-93039","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"dmaengine: dw-edma: Serialize channel state checks","id":"CVE-2026-93040"},"packages":[],"prev":{"headline":"iio: dac: ad5686: missing NULL check on match data","id":"CVE-2026-93038"},"products":["Linux"],"published":"2026-09-17","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":"A use-after-free vulnerability in the Linux kernel's Meson audio driver allows attackers to potentially execute code or escalate privileges via a double free error during memory reallocation failures.","url":"https://insights.sbomify.com/CVE-2026-93039/"}