{
  "id": "CVE-2026-90030",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-90030",
  "published_at": "2026-09-16T10:33:31.801Z",
  "title": "usb: dwc3: clear forceRM when issuing EndTransfer",
  "vendor": "Linux",
  "product": "Linux",
  "cvss": {
    "score": 7.8,
    "source": "cna",
    "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "In the Linux kernel, the following vulnerability has been resolved:\n\nusb: dwc3: clear forceRM when issuing EndTransfer\n\nThe forceRM bit of the DEPCMD register controls the behavior of the\nEndTransfer command used to stop an active transfer. Older DWC3\nprogramming guide revisions recommended setting forceRM=1 when\nissuing EndTransfer. Newer programming guide revisions recommend\nissuing EndTransfer with forceRM cleared.\n\nWith forceRM=1 on DWC_usb31 v2.00a and v2.10a controllers, a transfer\naborted through the ep_dequeue path was observed to remain active\nafter EndTransfer completion. A subsequent StartTransfer issued on the\nsame endpoint triggered writes associated with the aborted transfer.\nThis resulted in an SMMU fault because the transfer buffer had already\nbeen unmapped during EndTransfer command-completion cleanup.\n\nUsing forceRM=0 eliminates the issue. Although older DWC3 programming\nguide revisions recommended setting forceRM=1, no issues are known\nfrom using forceRM=0. Clear forceRM when issuing EndTransfer to provide\nconsistent EndTransfer behavior and align with newer programming guide\nrecommendations.",
  "cvss_by_source": {
    "cna": 7.8
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "\u003e= ab99c4be945724b032cc55e05c6738fe1d84bf70, \u003c 7a50e138fa28e5ba76b11af66ed41cc300c0f2be",
          "\u003e= 1e43c86d84fb0503e82a143e017f35421498fc1a, \u003c 9f1e57c484f9edeaaa5a27a03ed985e98496e81d",
          "\u003e= 1e43c86d84fb0503e82a143e017f35421498fc1a, \u003c 0afe5c31612de3d18cc6d16e616da4a48ba1e5a2",
          "\u003e= 1e43c86d84fb0503e82a143e017f35421498fc1a, \u003c e01408ee52fe5cb2d0b43f47f359336af2b6c316",
          "\u003e= 1e43c86d84fb0503e82a143e017f35421498fc1a, \u003c b58e6200450d350314db0ecda7d6d1bde3281e80",
          "\u003e= 6.6.37, \u003c 6.6.160"
        ],
        "fixed_in": [
          "7a50e138fa28e5ba76b11af66ed41cc300c0f2be",
          "9f1e57c484f9edeaaa5a27a03ed985e98496e81d",
          "0afe5c31612de3d18cc6d16e616da4a48ba1e5a2",
          "e01408ee52fe5cb2d0b43f47f359336af2b6c316",
          "b58e6200450d350314db0ecda7d6d1bde3281e80",
          "6.6.160"
        ]
      },
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "6.9"
        ],
        "fixed_in": [
          "0",
          "6.6.160",
          "6.12.112",
          "6.18.51",
          "7.2.5",
          "7.3"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Linux to 7a50e138fa28e5ba76b11af66ed41cc300c0f2be or 9f1e57c484f9edeaaa5a27a03ed985e98496e81d or 0afe5c31612de3d18cc6d16e616da4a48ba1e5a2 or e01408ee52fe5cb2d0b43f47f359336af2b6c316 or b58e6200450d350314db0ecda7d6d1bde3281e80 or 6.6.160 or later.",
      "Upgrade Linux to 0 or 6.6.160 or 6.12.112 or 6.18.51 or 7.2.5 or 7.3 or later."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
