# CVE-2026-89939: iio: chemical: atlas-sensor: fix PM reference leak in buffer postenable

> A reference leak in the Atlas sensor driver prevents device autosuspend, potentially causing resource exhaustion and denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-101495, BELL-CVE-2026-89939, DEBIAN-CVE-2026-89939, GHSA-w73m-f97h-p6pv, UBUNTU-CVE-2026-89939

## What is CVE-2026-89939?

CVE-2026-89939 is a denial of service 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.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

iio: chemical: atlas-sensor: fix PM reference leak in buffer postenable

atlas_buffer_postenable() acquires a runtime PM reference with
pm_runtime_resume_and_get() but returns the result of
atlas_set_interrupt() directly. If atlas_set_interrupt() fails,
the runtime PM reference is leaked and the device can never
autosuspend.

Add pm_runtime_put_autosuspend() on the error path to balance
the reference.

## Which versions are affected by CVE-2026-89939?


## How do I fix CVE-2026-89939?

Apply the vendor's patch.

## Is CVE-2026-89939 being exploited?

There is no known exploitation of CVE-2026-89939 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-89939 and fix it if it is affected.

What it is: CVE-2026-89939 is a denial of service 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.
Exploitation: There is no known exploitation of CVE-2026-89939 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-89939/ (Markdown: https://insights.sbomify.com/CVE-2026-89939/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-89939
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-89939
- OSV: https://osv.dev/vulnerability/CVE-2026-89939

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-89939/
Summaries are generated and may contain mistakes; the official description above is the record.