Unknown

CVE-2026-98919 — drm/xe: harden adjust_idledly() against divide-by-zero and overflow

In the Linux kernel, the following vulnerability has been resolved: drm/xe: harden adjust_idledly() against divide-by-zero and overflow adjust_idledly() has several corner-case issues flagged during review: 1. If xe_gt_clock_init() failed to recognise the crystal clock, gt->info.timestamp_base is 0, which makes idledly_units_ps also 0. The subsequent DIV_ROUND_CLOSEST(..., idledly_units_ps) is then a divide-by-zero and panics the kernel. 2. The tick-to-ns conversions are done in u32: idledly * idledly_units_ps, (maxcnt - 1) * 1000 Both overflow u32 before DIV_ROUND_CLOSEST() sees them. 3. If IDLE_WAIT_TIME reads back as 0, maxcnt evaluates to 0 and the maxcnt - 1 clamp wraps to 0xFFFFFFFF in u32. 4. The register only stores whole ticks, so the clamped ns value has to be converted to ticks and back. DIV_ROUND_CLOSEST() can round that conversion up past maxcnt: maxcnt = 640 ns, one tick = 666664 ps clamp: maxcnt - 1 = 639 ns ns -> ticks: 639000 / 666664 = 0.958 -> rounds to 1 tick tick -> ns: 1 * 666664 / 1000 = 667 ns 667 ns is programmed into RING_IDLEDLY, but 667 >= maxcnt (640), so xe_gt_WARN_ON() fires again on every subsequent init. Return early if timestamp_base is 0 (the unknown-crystal path). Do the conversions in u64 via the *_ULL() helpers so they cannot wrap. Clamp with a floor (DIV_ROUND_DOWN_ULL) so the programmed delay stays strictly below maxcnt, and guard the maxcnt == 0 case with a zero delay while still writing RING_IDLEDLY so INHIBIT_SWITCH_UNTIL_PREEMPTED is cleared. v2: Drop the redundant warn on the timestamp_base == 0 path; xe_gt_clock_init() already warns on an unrecognised crystal clock. Keep the early return to avoid the divide-by-zero. - Vinay v3: Field-mask the RING_IDLEDLY write with REG_FIELD_PREP(IDLE_DELAY, ...) instead of writing the raw tick count, which could clobber INHIBIT_SWITCH_UNTIL_PREEMPTED and reserved bits. Split the inhibit-switch clear from the maxcnt clamp so a set inhibit bit no longer forces a needless delay overwrite when the delay itself is already valid. Use gt_to_xe(gt) instead of gt_to_xe(hwe->gt). (cherry picked from commit d864065ea25e9d12897c175de9176ce46677e176)

Published Oct 23, 2026 · Updated Oct 23, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+1

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.17%

ahead of 7% of scored CVEs · Oct 30, 2026

Affects

Linux

CVSS base

—

Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	≥ d2de4410a88ffc6053300d03041cc73b8c85dbaf and < 2bcbfc5e7bfa9cc76818c54db698da5bdc13d9ff≥ d2de4410a88ffc6053300d03041cc73b8c85dbaf and < 531d4cd03118224022dc21ae25af052ce2a9e267≥ d2de4410a88ffc6053300d03041cc73b8c85dbaf and < 90f467577ebc28c5bc4ba2f0f1b83a4419fb0740version 6.15	Vulnerable	CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 24, 2026 → Oct 30, 2026 · 7 reading(s) · max 0.21%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Not enough vector or weakness data: use the affected application’s logs as a starting point.

application logs

Timeline

What happened to this CVE, newest first.

2026
Record published
Oct 23, 2026
Affected products added · linux/linux
Oct 23, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 23, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 23, 2026 · Alertas do Telegram
CVE published
Oct 23, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 23, 2026 – Oct 23, 2026
1× Official description updated · Oct 23, 2026 – Oct 23, 2026

References

3 on the record

git.kernel.org/stable/c/90f467577ebc28c5bc4ba2f0f1b83a4419fb0740
NIST National Vulnerability Database
git.kernel.org/stable/c/2bcbfc5e7bfa9cc76818c54db698da5bdc13d9ff
NIST National Vulnerability Database
git.kernel.org/stable/c/531d4cd03118224022dc21ae25af052ce2a9e267
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 3d
Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 3d
Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 3d
Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 3d
Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 3d
Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 3d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No CVSS score published by NVD, the CNA, CISA or GitHub so far.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-98919 is "drm/xe: harden adjust_idledly() against divide-by-zero and overflow", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.