CVE-2026-68103 (GCVE-0-2026-68103)
Vulnerability from cvelistv5
Published
2026-08-10 11:58
Modified
2026-10-19 20:58
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: reject mapping a reserved doorbell to a new queue When creating an user-queue, the user space provides a doorbell BO handle and an offset within the bo to obtain a doorbell. However current implementation using xa_store_irq() to store a doorbell, which allows a later queue created with the same BO and offset parameters to overwrite an existing queue and doorbell mapping. This can cause problems like misrouting fence IRQ processing to a wrong queue, and mislead the cleanup process of one queue erasing the mapping of another queue. This commit fixes this issue by replacing xa_store_irq with xa_insert_irq, which rejects mapping a reserved doorbell to a newly created queue (cherry picked from commit 6244eae22966350db52faf9c1369d3b2ffc5de4e)
Impacted products
Vendor Product Version
Linux Linux Version: 8949843762631d9d0fc526dfb61a272dca29fc6f
Version: 8949843762631d9d0fc526dfb61a272dca29fc6f
Create a notification for this product.
Show details on NVD website


{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-68103",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-10-16T15:43:48.984694Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "problemTypes": [
          {
            "descriptions": [
              {
                "cweId": "CWE-662",
                "description": "CWE-662 Improper Synchronization",
                "lang": "en",
                "type": "CWE"
              }
            ]
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-10-19T20:58:50.510Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "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": "1050d258c7c56066d2dcaedf8d0ef66364062adc",
              "status": "affected",
              "version": "8949843762631d9d0fc526dfb61a272dca29fc6f",
              "versionType": "git"
            },
            {
              "lessThan": "a609b6278bf3cde17eeee6620091465521e4b02c",
              "status": "affected",
              "version": "8949843762631d9d0fc526dfb61a272dca29fc6f",
              "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": "6.16"
            },
            {
              "lessThan": "6.16",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.1.*",
              "status": "unaffected",
              "version": "7.1.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.2",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1.6",
                  "versionStartIncluding": "6.16",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2",
                  "versionStartIncluding": "6.16",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: reject mapping a reserved doorbell to a new queue\n\nWhen creating an user-queue, the user space\nprovides a doorbell BO handle and an offset within\nthe bo to obtain a doorbell.\n\nHowever current implementation using xa_store_irq()\nto store a doorbell, which allows a later queue created\nwith the same BO and offset parameters to overwrite an\nexisting queue and doorbell mapping.\n\nThis can cause problems like misrouting fence IRQ\nprocessing to a wrong queue, and mislead the cleanup\nprocess of one queue erasing the mapping of another queue.\n\nThis commit fixes this issue by replacing xa_store_irq with\nxa_insert_irq, which rejects mapping a reserved\ndoorbell to a newly created queue\n\n(cherry picked from commit 6244eae22966350db52faf9c1369d3b2ffc5de4e)"
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.1,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The bug is reached only through the AMDGPU DRM_USERQ ioctl on a local render node (/dev/dri/renderD*); fence IRQ handling is driven by local GPU completion events, not remote network input.\nAC:L - An attacker can deterministically trigger the overwrite by issuing AMDGPU_USERQ_OP_CREATE with the same doorbell GEM handle and offset (same process) or by landing on the same global doorbell BAR index (shared-GPU hosts); no race or victim timing is required.\nPR:L - Exploitation requires only access to the AMDGPU render node granted to normal local users (e.g., render/video group on workstations, cloud GPU VMs, ROCm compute nodes); high-priority queue creation is optional and not needed for the attack.\nUI:N - The attacker triggers the flaw directly via ioctls; victims need only be running ordinary GPU compute/graphics workloads on the same device, with no additional user interaction.\nS:U - Impact is confined to kernel AMDGPU user-queue and fence state on the local GPU; it does not cross VM, IOMMU, or sandbox boundaries into another security authority.\nC:N - Misrouting fence IRQs corrupts queue-to-doorbell associations and synchronization but provides no kernel or victim memory read primitive; AMDGPU per-process VM isolation blocks direct disclosure of another tenant\u0027s GPU buffers.\nI:H - Silently overwriting the device-global doorbell xarray lets an attacker hijack another queue\u0027s fence IRQ handling and erase its mapping on teardown, corrupting kernel queue state and breaking GPU synchronization integrity for other workloads.\nA:H - Orphaned queues stop receiving fence IRQs, provoking hang detection and amdgpu_userq_mgr_reset_work paths that can force per-queue or full GPU recovery, denying GPU service to all users on shared AMD GPU systems."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-17T04:58:51.492Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/1050d258c7c56066d2dcaedf8d0ef66364062adc"
        },
        {
          "url": "https://git.kernel.org/stable/c/a609b6278bf3cde17eeee6620091465521e4b02c"
        }
      ],
      "title": "drm/amdgpu: reject mapping a reserved doorbell to a new queue",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-68103",
    "datePublished": "2026-08-10T11:58:19.317Z",
    "dateReserved": "2026-07-30T09:28:09.368Z",
    "dateUpdated": "2026-10-19T20:58:50.510Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2026-68103\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-10-16T15:43:48.984694Z\"}}}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-662\", \"description\": \"CWE-662 Improper Synchronization\"}]}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-10-16T15:43:49.652Z\"}}], \"cna\": {\"title\": \"drm/amdgpu: reject mapping a reserved doorbell to a new queue\", \"metrics\": [{\"cvssV3_1\": {\"version\": \"3.1\", \"baseScore\": 7.1, \"baseSeverity\": \"HIGH\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"AV:L - The bug is reached only through the AMDGPU DRM_USERQ ioctl on a local render node (/dev/dri/renderD*); fence IRQ handling is driven by local GPU completion events, not remote network input.\\nAC:L - An attacker can deterministically trigger the overwrite by issuing AMDGPU_USERQ_OP_CREATE with the same doorbell GEM handle and offset (same process) or by landing on the same global doorbell BAR index (shared-GPU hosts); no race or victim timing is required.\\nPR:L - Exploitation requires only access to the AMDGPU render node granted to normal local users (e.g., render/video group on workstations, cloud GPU VMs, ROCm compute nodes); high-priority queue creation is optional and not needed for the attack.\\nUI:N - The attacker triggers the flaw directly via ioctls; victims need only be running ordinary GPU compute/graphics workloads on the same device, with no additional user interaction.\\nS:U - Impact is confined to kernel AMDGPU user-queue and fence state on the local GPU; it does not cross VM, IOMMU, or sandbox boundaries into another security authority.\\nC:N - Misrouting fence IRQs corrupts queue-to-doorbell associations and synchronization but provides no kernel or victim memory read primitive; AMDGPU per-process VM isolation blocks direct disclosure of another tenant\u0027s GPU buffers.\\nI:H - Silently overwriting the device-global doorbell xarray lets an attacker hijack another queue\u0027s fence IRQ handling and erase its mapping on teardown, corrupting kernel queue state and breaking GPU synchronization integrity for other workloads.\\nA:H - Orphaned queues stop receiving fence IRQs, provoking hang detection and amdgpu_userq_mgr_reset_work paths that can force per-queue or full GPU recovery, denying GPU service to all users on shared AMD GPU systems.\"}]}], \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"8949843762631d9d0fc526dfb61a272dca29fc6f\", \"lessThan\": \"1050d258c7c56066d2dcaedf8d0ef66364062adc\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"8949843762631d9d0fc526dfb61a272dca29fc6f\", \"lessThan\": \"a609b6278bf3cde17eeee6620091465521e4b02c\", \"versionType\": \"git\"}], \"programFiles\": [\"drivers/gpu/drm/amd/amdgpu/amdgpu_userq.c\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"6.16\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"6.16\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"7.1.6\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"7.1.*\"}, {\"status\": \"unaffected\", \"version\": \"7.2\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"drivers/gpu/drm/amd/amdgpu/amdgpu_userq.c\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/1050d258c7c56066d2dcaedf8d0ef66364062adc\"}, {\"url\": \"https://git.kernel.org/stable/c/a609b6278bf3cde17eeee6620091465521e4b02c\"}], \"x_generator\": {\"engine\": \"bippy-1.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\ndrm/amdgpu: reject mapping a reserved doorbell to a new queue\\n\\nWhen creating an user-queue, the user space\\nprovides a doorbell BO handle and an offset within\\nthe bo to obtain a doorbell.\\n\\nHowever current implementation using xa_store_irq()\\nto store a doorbell, which allows a later queue created\\nwith the same BO and offset parameters to overwrite an\\nexisting queue and doorbell mapping.\\n\\nThis can cause problems like misrouting fence IRQ\\nprocessing to a wrong queue, and mislead the cleanup\\nprocess of one queue erasing the mapping of another queue.\\n\\nThis commit fixes this issue by replacing xa_store_irq with\\nxa_insert_irq, which rejects mapping a reserved\\ndoorbell to a newly created queue\\n\\n(cherry picked from commit 6244eae22966350db52faf9c1369d3b2ffc5de4e)\"}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"7.1.6\", \"versionStartIncluding\": \"6.16\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"7.2\", \"versionStartIncluding\": \"6.16\"}], \"operator\": \"OR\"}]}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2026-08-17T04:58:51.492Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2026-68103\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-10-19T20:58:50.510Z\", \"dateReserved\": \"2026-07-30T09:28:09.368Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2026-08-10T11:58:19.317Z\", \"assignerShortName\": \"Linux\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…

Loading…