CVE-2026-98919: Linux kernel · drm/xe: harden adjust_idledly() against divide-by-zero and overflow
Source GCVE Database
Not known to be exploited · fixed in 531d4cd03118224022dc21ae25af052ce2a9e267 : patch Linux kernel soon.
Data as of 26 Oct 2026, 17:16 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 531d4cd03118224022dc21ae25af052ce2a9e267, 90f467577ebc28c5bc4ba2f0f1b83a4419fb0740, 2bcbfc5e7bfa9cc76818c54db698da5bdc13d9ff
Exploitation evidence
Disclosed: evidence found.
CVE published 23 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.
What to do
Upgrade Linux kernel to 531d4cd03118224022dc21ae25af052ce2a9e267, 90f467577ebc28c5bc4ba2f0f1b83a4419fb0740 or 2bcbfc5e7bfa9cc76818c54db698da5bdc13d9ff.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented in the Linux kernel to address these issues. The patch includes early returns to prevent divide-by-zero, use of 64-bit arithmetic to avoid overflow, and proper clamping and masking of hardware register writes. Users should update to the fixed Linux kernel version containing this patch.
Description
A vulnerability in the Linux kernel's drm/xe component related to the adjust_idledly() function has been resolved. The function had multiple issues including a divide-by-zero error when an unrecognized crystal clock caused a zero timestamp base, and integer overflow problems in tick-to-nanosecond conversions. These issues could cause kernel panics or repeated warnings during initialization. The fix involves early returns to avoid divide-by-zero, using 64-bit arithmetic to prevent overflow, and careful clamping of delay values to avoid invalid programming of hardware registers.
References
- nvd.nist.gov/vuln/detail/CVE-2026-98919 (opens in a new tab)
- git.kernel.org/stable/c/2bcbfc5e7bfa9cc76818c54db698da5bdc13d9ff (opens in a new tab)
- git.kernel.org/stable/c/531d4cd03118224022dc21ae25af052ce2a9e267 (opens in a new tab)
- git.kernel.org/stable/c/90f467577ebc28c5bc4ba2f0f1b83a4419fb0740 (opens in a new tab)