# CVE-2026-98679: iio: accel: kxcjk-1013: reject duplicate event disable

> A local attacker can trigger a runtime PM usage count underflow in the kxcjk-1013 accelerometer driver, potentially causing a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-109061, BELL-CVE-2026-98679, DEBIAN-CVE-2026-98679, GHSA-jg4r-9rqj-mgw5, UBUNTU-CVE-2026-98679

## What is CVE-2026-98679?

CVE-2026-98679 is a denial of service vulnerability in Linux, published on 18 Oct 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: accel: kxcjk-1013: reject duplicate event disable

The IIO core does not filter duplicate writes to the event enable
attribute. kxcjk1013_write_event_config() already ignores repeated
enable requests, but a repeated disable request still calls
kxcjk1013_set_power_state(data, false), dropping a runtime PM reference
that was not acquired for this request. This can underflow the runtime
PM usage count and trigger a "Runtime PM usage count underflow" warning.

Return early when the requested state already matches ev_enable_state.

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


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

Apply the vendor's patch.

## Is CVE-2026-98679 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98679 is a denial of service vulnerability in Linux, published on 18 Oct 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-98679 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-98679/ (Markdown: https://insights.sbomify.com/CVE-2026-98679/index.md)
```

## Sources

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

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