# CVE-2026-98500: HID: hid-oxp: use cancel_delayed_work_sync() in remove

> A race condition in the Linux kernel HID driver allows concurrent access to a closed device, potentially causing a system crash or 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:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-98500, GHSA-j346-48rx-v5qm, UBUNTU-CVE-2026-98500

## What is CVE-2026-98500?

CVE-2026-98500 is a 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:

HID: hid-oxp: use cancel_delayed_work_sync() in remove

oxp_hid_remove() uses cancel_delayed_work() for all three delayed work
items.  cancel_delayed_work() only dequeues a pending work item without
waiting for a currently executing callback to finish.  If any of the
work callbacks (oxp_rgb_queue_fn, oxp_btn_queue_fn, oxp_mcu_init_fn) is
running at the time of removal, the callback continues executing
concurrently with hid_hw_close() and hid_hw_stop(), accessing the HID
device after it has been closed and stopped.

Use cancel_delayed_work_sync() instead to ensure that any in-progress
work callback completes before device teardown proceeds.

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


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

Apply the vendor's patch.

## Is CVE-2026-98500 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98500 is a 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-98500 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-98500/ (Markdown: https://insights.sbomify.com/CVE-2026-98500/index.md)
```

## Sources

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

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