Kernel fault via unchecked teardown operations pointer
Published Oct 23, 2026 · Updated Oct 23, 2026
Null dereference in Linux host1x exposes systems to a kernel fault during initialization-error cleanup via an unchecked operations pointer. In host1x_device_init(), the teardown and teardown_late paths read client->ops->exit and client->ops->late_exit without checking whether client->ops is NULL. Triggering requires initialization failure and a client without operations; the maintainer states that existing clients provide operations, and no attacker-controlled trigger is documented.
Summary
What happened
Null dereference in Linux host1x exposes systems to a kernel fault during initialization-error cleanup via an unchecked operations pointer. In host1x_device_init(), the teardown and teardown_late paths read client->ops->exit and client->ops->late_exit without checking whether client->ops is NULL. Triggering requires initialization failure and a client without operations; the maintainer states that existing clients provide operations, and no attacker-controlled trigger is documented.
The record
- CVE
- CVE-2026-98876
- Published
- Oct 23, 2026
- Updated
- Oct 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 23, 2026CVE publishedPublication date reported by the CVE source.
- Oct 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <5.15.222
- Affected versionversion=0 <6.1.189
- Affected versionversion=0 <6.12.111
- Affected versionversion=0 <6.18.53
- Affected versionversion=0 <6.6.158
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <29375e071ea201fe97bafe1d2ad9d9f30311abfb
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <62851e7b0e55de6fe08da08bc41fd587fbcb0e9b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <71d25f668bc5c0f36ea843462e12307dea45aaa3
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <74bd1f05d9ba2d6672d30ccafe80a38104c1f73f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d8d5b6e02fc281dea33d6b0b0fadaccea56f2067
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f1fa6c936fa9de80ae446ba5e76e227e991b8e56
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us