FKIE_CVE-2026-23009

Vulnerability from fkie_nvd - Published: 2026-01-25 15:15 - Updated: 2026-01-26 15:03
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: xhci: sideband: don't dereference freed ring when removing sideband endpoint xhci_sideband_remove_endpoint() incorrecly assumes that the endpoint is running and has a valid transfer ring. Lianqin reported a crash during suspend/wake-up stress testing, and found the cause to be dereferencing a non-existing transfer ring 'ep->ring' during xhci_sideband_remove_endpoint(). The endpoint and its ring may be in unknown state if this function is called after xHCI was reinitialized in resume (lost power), or if device is being re-enumerated, disconnected or endpoint already dropped. Fix this by both removing unnecessary ring access, and by checking ep->ring exists before dereferencing it. Also make sure endpoint is running before attempting to stop it. Remove the xhci_initialize_ring_info() call during sideband endpoint removal as is it only initializes ring structure enqueue, dequeue and cycle state values to their starting values without changing actual hardware enqueue, dequeue and cycle state. Leaving them out of sync is worse than leaving it as it is. The endpoint will get freed in after this in most usecases. If the (audio) class driver want's to reuse the endpoint after offload then it is up to the class driver to ensure endpoint is properly set up.
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/34f6634dba87ef72b3c3a3a524be663adef7ab42
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/dd83dc1249737b837ac5d57c81f2b0977c613d9f
Impacted products
Vendor Product Version
To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nxhci: sideband: don\u0027t dereference freed ring when removing sideband endpoint\n\nxhci_sideband_remove_endpoint() incorrecly assumes that the endpoint is\nrunning and has a valid transfer ring.\n\nLianqin reported a crash during suspend/wake-up stress testing, and\nfound the cause to be dereferencing a non-existing transfer ring\n\u0027ep-\u003ering\u0027 during xhci_sideband_remove_endpoint().\n\nThe endpoint and its ring may be in unknown state if this function\nis called after xHCI was reinitialized in resume (lost power), or if\ndevice is being re-enumerated, disconnected or endpoint already dropped.\n\nFix this by both removing unnecessary ring access, and by checking\nep-\u003ering exists before dereferencing it. Also make sure endpoint is\nrunning before attempting to stop it.\n\nRemove the xhci_initialize_ring_info() call during sideband endpoint\nremoval as is it only initializes ring structure enqueue, dequeue and\ncycle state values to their starting values without changing actual\nhardware enqueue, dequeue and cycle state. Leaving them out of sync\nis worse than leaving it as it is. The endpoint will get freed in after\nthis in most usecases.\n\nIf the (audio) class driver want\u0027s to reuse the endpoint after offload\nthen it is up to the class driver to ensure endpoint is properly set up."
    },
    {
      "lang": "es",
      "value": "En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\n\nxhci: banda lateral: no desreferenciar el anillo liberado al eliminar el punto final de banda lateral\n\nxhci_sideband_remove_endpoint() asume incorrectamente que el punto final est\u00e1 en ejecuci\u00f3n y tiene un anillo de transferencia v\u00e1lido.\n\nLianqin inform\u00f3 de un fallo durante las pruebas de estr\u00e9s de suspensi\u00f3n/activaci\u00f3n, y encontr\u00f3 que la causa era la desreferenciaci\u00f3n de un anillo de transferencia inexistente \u0027ep-\u0026gt;ring\u0027 durante xhci_sideband_remove_endpoint().\n\nEl punto final y su anillo pueden estar en un estado desconocido si esta funci\u00f3n se llama despu\u00e9s de que xHCI fuera reinicializado en la reanudaci\u00f3n (p\u00e9rdida de energ\u00eda), o si el dispositivo est\u00e1 siendo reenumerado, desconectado o el punto final ya ha sido descartado.\n\nSolucione esto eliminando el acceso innecesario al anillo y comprobando que \u0027ep-\u0026gt;ring\u0027 existe antes de desreferenciarlo. Tambi\u00e9n aseg\u00farese de que el punto final est\u00e9 en ejecuci\u00f3n antes de intentar detenerlo.\n\nElimine la llamada a xhci_initialize_ring_info() durante la eliminaci\u00f3n del punto final de banda lateral, ya que solo inicializa los valores de estado de encolamiento, desencolamiento y ciclo de la estructura del anillo a sus valores iniciales sin cambiar el estado real de encolamiento, desencolamiento y ciclo del hardware. Dejarlos fuera de sincronizaci\u00f3n es peor que dejarlo como est\u00e1. El punto final ser\u00e1 liberado despu\u00e9s de esto en la mayor\u00eda de los casos de uso.\n\nSi el controlador de clase (de audio) desea reutilizar el punto final despu\u00e9s de la descarga, entonces es responsabilidad del controlador de clase asegurar que el punto final est\u00e9 configurado correctamente."
    }
  ],
  "id": "CVE-2026-23009",
  "lastModified": "2026-01-26T15:03:33.357",
  "metrics": {},
  "published": "2026-01-25T15:15:55.767",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/34f6634dba87ef72b3c3a3a524be663adef7ab42"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/dd83dc1249737b837ac5d57c81f2b0977c613d9f"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Awaiting Analysis"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

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.



Detection rules are retrieved from Rulezet.