Quick answers
- Is CVE-2026-98876 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-98876 being exploited in the wild.
- How severe is CVE-2026-98876?
- Informational severity, published 23 October 2026.
- Which products and versions are affected?
- Unknown Linux kernel Affected versions prior to commit 71d25f668bc5c0f36ea843462e12307dea45aaa3.
- Is there a fix for CVE-2026-98876?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-98876 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-98876?
- Check whether you run Unknown Linux kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The host1x_device_init() function in drivers/gpu/host1x/bus.c lacks NULL checks on client->ops in its error teardown paths (teardown and teardown_late labels), unlike the forward init paths which guard with 'client->ops &&'. A NULL pointer dereference can occur if client->ops is NULL during error teardown, requiring a NULL check to be added before dereferencing client->ops->exit and client->ops->late_exit.
Affected products
- <UNKNOWN> Linux kernel Affected versions prior to commit 71d25f668bc5c0f36ea843462e12307dea45aaa3
Timeline
- 2026-10-23: disclosed