{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89942 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89942 is a high-severity use after free vulnerability in Linux, published on 16 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-89942 and fix it if it is affected.\n\nWhat it is: CVE-2026-89942 is a high-severity use after free vulnerability in Linux, published on 16 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-89942 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-89942/ (Markdown: https://insights.sbomify.com/CVE-2026-89942/index.md)","id":"CVE-2026-89942","markdown":"https://insights.sbomify.com/CVE-2026-89942/index.md","name":"CVE-2026-89942","record":{"aliases":["BELL-CVE-2026-89942","DEBIAN-CVE-2026-89942","GHSA-3g64-jv43-3qjf","UBUNTU-CVE-2026-89942"],"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 IIO","requires_auth":"low_privilege","summary":"A use-after-free in the Linux kernel IIO subsystem allows local attackers to execute arbitrary code or escalate privileges via anonymous buffer release.","user_interaction":"not_required","vuln_class":"use_after_free"},"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\niio: buffer: Fix potential use-after-free in anonymous buffer release\n\nAn anonymous buffer handle holds a reference to the underlying IIO device.\nThe reference is dropped in the buffer handle's release function. If the\ndevice has been removed, either through unbind or hot-unplug, the buffer\nhandle might hold the last reference.\n\nThe release function takes the mutex for the buffer using a guard, which\nmeans the unlock happens after all the code in the function, including\n`iio_device_put()`. If the anonymous buffer holds the last reference this\nmight free both the IIO device and the buffer, which contains the mutex,\nleading to use-after-free when the mutex is unlocked.\n\nFix this by using a scoped guard just around the buffer dmabuf list access,\nmaking sure the mutex is unlocked before releasing the IIO device.\n\nVersion 10 of the patch that introduced this issue used this exact scheme\nof first unlocking and then dropping the reference [1]. During review it\nwas suggested to use a guard instead, and version 11 made that change [2].","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":"iio: buffer: Fix potential use-after-free in anonymous buffer release","id":"CVE-2026-89942","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"ASoC: loongson: Fix error handling in ACPI property parsing","id":"CVE-2026-89943"},"packages":[],"prev":{"headline":"iio: buffer: Make IIO DMA fence release RCU-safe","id":"CVE-2026-89941"},"products":["Linux"],"published":"2026-09-16","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 in the Linux kernel IIO subsystem allows local attackers to execute arbitrary code or escalate privileges via anonymous buffer release.","url":"https://insights.sbomify.com/CVE-2026-89942/"}