Skip to content
statance
MenuClose
unknown

CVE-2026-98177

drm/amdkfd: Avoid integer underflow in EOP ring size calculation.

Published 6 Oct 2026 · Source updated 10 Nov 2026 · Retrieved 2026-11-19 03:50 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

In the Linux kernel, the following vulnerability has been resolved:

drm/amdkfd: Avoid integer underflow in EOP ring size calculation.

The low 6 bits of cp_hqd_eop_control store the base-2 logarithm of the EOP ring size. This was calculated as

order_base_2(q->eop_ring_buffer_size / 4) - 1

But order_base_2 can in theory return 0, so this could underflow (although in practice the ring buffer size cannot be less than 4096).

Change this to

order_base_2(q->eop_ring_buffer_size / 8)

using properties of logarithms.

Also add to the above comment to make the mathematics more clear.

(cherry picked from commit f0f43fcf8b2b3a924cad9444340921c96ed5f634)

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
LinuxLinuxaffected: d696d536f0a97ac779d6176107ac4e96d0a2f8b9 to < 85f2d80a260f2ee90647da094b80a2d5ce719750; affected: d696d536f0a97ac779d6176107ac4e96d0a2f8b9 to < 3c97f7cb6c48826663648b6081b614c2befc8ac7; affected: d696d536f0a97ac779d6176107ac4e96d0a2f8b9 to < 287a34c4d712e0bdb67751e21316d9c8d75a528a; affected: d696d536f0a97ac779d6176107ac4e96d0a2f8b9 to < 8ee521b8b189799e361d4233c5180ba56656d4d4See vendor advisory
LinuxLinuxaffected: 4.3; unaffected: 0 to < 4.3; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.2.8 to ≤ 7.2.*; unaffected: 7.3 to ≤ *See vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-19 21:16 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed