{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89938 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89938 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-89938 and fix it if it is affected.\n\nWhat it is: CVE-2026-89938 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-89938 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-89938/ (Markdown: https://insights.sbomify.com/CVE-2026-89938/index.md)","id":"CVE-2026-89938","markdown":"https://insights.sbomify.com/CVE-2026-89938/index.md","name":"CVE-2026-89938","record":{"aliases":["AZL-101132","BELL-CVE-2026-89938","DEBIAN-CVE-2026-89938","GHSA-cv98-fww9-9mfg","UBUNTU-CVE-2026-89938"],"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 driver","requires_auth":"low_privilege","summary":"A use-after-free in the Linux kernel Atlas sensor driver allows attackers to execute arbitrary code or escalate privileges via race conditions during device removal.","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: chemical: atlas-sensor: use iio_trigger_poll_nested() to fix remove UAF\n\nThe atlas driver requests its hardware data-ready IRQ with\ndevm_request_threaded_irq(); its threaded handler queues an irq_work,\natlas_work_handler(), that calls iio_trigger_poll(data-\u003etrig).\n\nThe IRQ is devm-managed, so free_irq() runs from the devres unwind after\natlas_remove() returns without flushing that irq_work.  Once a buffer is\nenabled, conversion-complete IRQs keep firing and queueing it; a pending\nirq_work can therefore run after the unwind has freed atlas_data/indio_dev\nand the trigger, when atlas_work_handler() derives the atlas_data pointer\nvia container_of() and dereferences data-\u003etrig, a use-after-free.\n\nCall iio_trigger_poll_nested() directly from the threaded handler instead\nof bouncing through irq_work.  free_irq() then drains the threaded handler,\nclosing the window; other iio drivers with a threaded data-ready IRQ do the\nsame (e.g. bmi270).\n\nThis issue was found by an in-house static analysis tool.","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: chemical: atlas-sensor: use iio_trigger_poll_nested() to fix remove UAF","id":"CVE-2026-89938","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"iio: chemical: atlas-sensor: fix PM reference leak in buffer postenable","id":"CVE-2026-89939"},"packages":[],"prev":{"headline":"iio: chemical: sgp30: Handle IAQ thread creation failure","id":"CVE-2026-89937"},"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 Atlas sensor driver allows attackers to execute arbitrary code or escalate privileges via race conditions during device removal.","url":"https://insights.sbomify.com/CVE-2026-89938/"}