VulnerabilityPublished 18 Oct 2026

CVE-2026-98500: Linux kernel · HID: hid-oxp: use cancel_delayed_work_sync() in remove

Source GCVE Database

Authoritative record:CVE-2026-98500· Medium

Not known to be exploited : upgrade to eed737d89fa368251018a62e1d698958ef7dc635 or abd24922c2a9797d6184be0561dd85e7bcdfd091 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in eed737d89fa368251018a62e1d698958ef7dc635, abd24922c2a9797d6184be0561dd85e7bcdfd091

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-j346-48rx-v5qm

What to do

Upgrade Linux kernel to eed737d89fa368251018a62e1d698958ef7dc635 or abd24922c2a9797d6184be0561dd85e7bcdfd091.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 84910c459d65ab3a1aeac7f936169fb71334dd46, < eed737d89fa368251018a62e1d698958ef7dc635	Fixed in eed737d89fa368251018a62e1d698958ef7dc635
LinuxLinux	Affected ≥ 84910c459d65ab3a1aeac7f936169fb71334dd46, < abd24922c2a9797d6184be0561dd85e7bcdfd091	Fixed in abd24922c2a9797d6184be0561dd85e7bcdfd091
LinuxLinux	Affected =7.2	Fixed in–

AI-suggested

A fix is available that replaces cancel_delayed_work() with cancel_delayed_work_sync() in the oxp_hid_remove() function. Users should apply the updated Linux kernel version containing this fix to ensure proper synchronization during device removal.

Description

A vulnerability in the Linux kernel's hid-oxp driver was resolved by changing the removal function to use cancel_delayed_work_sync() instead of cancel_delayed_work(). The previous approach allowed delayed work callbacks to continue running concurrently with device teardown, potentially accessing the HID device after it was closed and stopped. This fix ensures that any in-progress work completes before the device is torn down.

Impact

The vulnerability could cause use-after-free or race conditions by allowing work callbacks to access the HID device after it has been closed and stopped. This may lead to undefined behavior or potential system instability. No information about exploitation in the wild is available.

Summary

The Linux kernel hid-oxp driver previously used cancel_delayed_work() in the oxp_hid_remove() function to cancel three delayed work items. However, cancel_delayed_work() only dequeues pending work without waiting for any currently executing callbacks to finish. This could lead to race conditions where callbacks (oxp_rgb_queue_fn, oxp_btn_queue_fn, oxp_mcu_init_fn) run concurrently with hid_hw_close() and hid_hw_stop(), accessing the device after it was closed. The vulnerability was resolved by replacing cancel_delayed_work() with cancel_delayed_work_sync(), which waits for any running work callbacks to complete before proceeding with device teardown.

References

Community reviews

Loading reviews…