CVE-2026-99630 (GCVE-0-2026-99630)
Vulnerability from cvelistv5 – Published: 2026-11-20 05:49 – Updated: 2026-11-20 05:49| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
4cdbba5a16aaf16513b69cc332b1d6f971a44b52 , < 2664f497d5e35384736e42fc59e5b9ef27ca791a
(git)
Affected: 4cdbba5a16aaf16513b69cc332b1d6f971a44b52 , < ce5f2a25bdf6b2bccfc4ffb5e4c5f12e97eeace1 (git) |
guessed | |
| Linux | Linux |
Affected:
7.2
Unaffected: 0 , < 7.2 (semver) Unaffected: 7.3.5 , ≤ 7.3.* (semver) Unaffected: 7.4-rc2 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/amd/amdgpu/amdgpu_userq.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "2664f497d5e35384736e42fc59e5b9ef27ca791a",
"status": "affected",
"version": "4cdbba5a16aaf16513b69cc332b1d6f971a44b52",
"versionType": "git"
},
{
"lessThan": "ce5f2a25bdf6b2bccfc4ffb5e4c5f12e97eeace1",
"status": "affected",
"version": "4cdbba5a16aaf16513b69cc332b1d6f971a44b52",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/amd/amdgpu/amdgpu_userq.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "7.2"
},
{
"lessThan": "7.2",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc2",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3.5",
"versionStartIncluding": "7.2",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.4-rc2",
"versionStartIncluding": "7.2",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu/userq: validate the moved individual BOs on restore\n\nAn individual BO of a user queue VM, i.e. one which doesn\u0027t share the\nroot reservation, goes to the individual needs_update list when it is\nevicted. The user queue restore looked at vm-\u003einvalidated for them, which\nthe VM state machine rework turned into the always_valid evicted list and\ncommit 18decfc9e8cc (\"drm/amdgpu/userq: actually validate userq BOs\")\ninto the individual evicted one. That list only holds imported DMA-bufs of\ncompute VMs though, so for a user queue VM nothing is validated.\n\nThe restore then neither locks such a BO nor moves it back. Its PTEs are\nupdated to wherever it is now, cleared if it went to system memory, and\nit doesn\u0027t get the new eviction fence, so it can move again under the\nrunning queue.\n\nOn navi48, once the BOs of an SDMA user queue are evicted from GTT\n(debugfs amdgpu_evict_gtt) the queue faults on its ring and rptr:\n\n amdgpu 0000:03:00.0: in page starting at address 0x0000000100000000 from client 10\n amdgpu 0000:03:00.0: \t Faulty UTCL2 client ID: SDMA0 (0xd)\n amdgpu 0000:03:00.0: in page starting at address 0x0000000100101000 from client 10\n\nValidate the BOs on the individual needs_update list like before.\n\n(cherry picked from commit eb0d94765d4be18d41e93ad09947dd9cc06ed31a)"
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T05:49:48.468Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/2664f497d5e35384736e42fc59e5b9ef27ca791a"
},
{
"url": "https://git.kernel.org/stable/c/ce5f2a25bdf6b2bccfc4ffb5e4c5f12e97eeace1"
}
],
"title": "drm/amdgpu/userq: validate the moved individual BOs on restore",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99630",
"datePublished": "2026-11-20T05:49:48.468Z",
"dateReserved": "2026-09-25T10:25:14.425Z",
"dateUpdated": "2026-11-20T05:49:48.468Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-99630",
"date": "2026-11-20",
"epss": "0.00156",
"percentile": "0.0483"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/amd/amdgpu/amdgpu_userq.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "2664f497d5e35384736e42fc59e5b9ef27ca791a",
"status": "affected",
"version": "4cdbba5a16aaf16513b69cc332b1d6f971a44b52",
"versionType": "git"
},
{
"lessThan": "ce5f2a25bdf6b2bccfc4ffb5e4c5f12e97eeace1",
"status": "affected",
"version": "4cdbba5a16aaf16513b69cc332b1d6f971a44b52",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/amd/amdgpu/amdgpu_userq.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "7.2"
},
{
"lessThan": "7.2",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc2",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu/userq: validate the moved individual BOs on restore\n\nAn individual BO of a user queue VM, i.e. one which doesn\u0027t share the\nroot reservation, goes to the individual needs_update list when it is\nevicted. The user queue restore looked at vm-\u003einvalidated for them, which\nthe VM state machine rework turned into the always_valid evicted list and\ncommit 18decfc9e8cc (\"drm/amdgpu/userq: actually validate userq BOs\")\ninto the individual evicted one. That list only holds imported DMA-bufs of\ncompute VMs though, so for a user queue VM nothing is validated.\n\nThe restore then neither locks such a BO nor moves it back. Its PTEs are\nupdated to wherever it is now, cleared if it went to system memory, and\nit doesn\u0027t get the new eviction fence, so it can move again under the\nrunning queue.\n\nOn navi48, once the BOs of an SDMA user queue are evicted from GTT\n(debugfs amdgpu_evict_gtt) the queue faults on its ring and rptr:\n\n amdgpu 0000:03:00.0: in page starting at address 0x0000000100000000 from client 10\n amdgpu 0000:03:00.0: \t Faulty UTCL2 client ID: SDMA0 (0xd)\n amdgpu 0000:03:00.0: in page starting at address 0x0000000100101000 from client 10\n\nValidate the BOs on the individual needs_update list like before.\n\n(cherry picked from commit eb0d94765d4be18d41e93ad09947dd9cc06ed31a)"
}
],
"id": "CVE-2026-99630",
"lastModified": "2026-11-20T06:17:56.060",
"metrics": {},
"published": "2026-11-20T06:17:56.060",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/2664f497d5e35384736e42fc59e5b9ef27ca791a"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/ce5f2a25bdf6b2bccfc4ffb5e4c5f12e97eeace1"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-20T10:20:29+00:00",
"cve": "CVE-2026-99630",
"id": "CVE-2026-99630",
"initial_release_date": "2026-11-20T05:49:48.468000+00:00",
"product_status:known_affected": "14",
"product_status:known_not_affected": "190",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: kernel: Denial of Service via improper buffer object validation in amdgpu user queues",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99630.json",
"version": "3"
}
}
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.