{
  "cveId": "CVE-2026-98919",
  "url": "https://patchblox.com/security/cve/CVE-2026-98919",
  "summary": "CVE-2026-98919 is fixed in linux on 1 platform by DEBIAN-CVE-2026-98919 (version 7.2.9-1), released October 24, 2026. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  drm/xe: harden adjust_idledly() against divide-b...",
  "description": "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-\u003Einfo.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 -\u003E ticks:  639000 / 666664   = 0.958 -\u003E rounds to 1 tick        tick -\u003E ns:    1 * 666664 / 1000 = 667 ns       667 ns is programmed into RING_IDLEDLY, but 667 \u003E= 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-\u003Egt).  (cherry picked from commit d864065ea25e9d12897c175de9176ce46677e176)",
  "published": "2026-10-23T13:17:12Z",
  "severity": "",
  "epss": 0.00174,
  "epssPercentile": 0.06884,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "7.2.9-1",
      "fix": "DEBIAN-CVE-2026-98919",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-98919",
      "released": "2026-10-24T13:25:57Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T19:12:23Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}