fkie_cve-2024-56680
Vulnerability from fkie_nvd
Published
2024-12-28 10:15
Modified
2024-12-28 10:15
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: media: intel/ipu6: do not handle interrupts when device is disabled Some IPU6 devices have shared interrupts. We need to handle properly case when interrupt is triggered from other device on shared irq line and IPU6 itself disabled. In such case we get 0xffffffff from ISR_STATUS register and handle all irq's cases, for what we are not not prepared and usually hang the whole system. To avoid the issue use pm_runtime_get_if_active() to check if the device is enabled and prevent suspending it when we handle irq until the end of irq. Additionally use synchronize_irq() in suspend
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/1429826883bb18847092b2e04c6598ef34bae1d4
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/57241487a3648515c9aa6fa89e31f2414eccfdbc
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/ed4524c87249edc3104f6bb28ab11325bed3d536
Impacted products
Vendor Product Version


To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: intel/ipu6: do not handle interrupts when device is disabled\n\nSome IPU6 devices have shared interrupts. We need to handle properly\ncase when interrupt is triggered from other device on shared irq line\nand IPU6 itself disabled. In such case we get 0xffffffff from\nISR_STATUS register and handle all irq\u0027s cases, for what we are not\nnot prepared and usually hang the whole system.\n\nTo avoid the issue use pm_runtime_get_if_active() to check if\nthe device is enabled and prevent suspending it when we handle irq\nuntil the end of irq. Additionally use synchronize_irq() in suspend"
    },
    {
      "lang": "es",
      "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: media: intel/ipu6: no gestionan interrupciones cuando el dispositivo est\u00e1 deshabilitado Algunos dispositivos IPU6 tienen interrupciones compartidas. Necesitamos gestionar adecuadamente el caso cuando la interrupci\u00f3n se activa desde otro dispositivo en la l\u00ednea irq compartida y el propio IPU6 est\u00e1 deshabilitado. En tal caso, obtenemos 0xffffffff del registro ISR_STATUS y gestionamos todos los casos de irq, para lo cual no estamos preparados y generalmente colgamos todo el sistema. Para evitar el problema, use pm_runtime_get_if_active() para verificar si el dispositivo est\u00e1 habilitado y evitar suspenderlo cuando gestionamos irq hasta el final de irq. Adem\u00e1s, usesynchronous_irq() en suspensi\u00f3n"
    }
  ],
  "id": "CVE-2024-56680",
  "lastModified": "2024-12-28T10:15:09.610",
  "metrics": {},
  "published": "2024-12-28T10:15:09.610",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/1429826883bb18847092b2e04c6598ef34bae1d4"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/57241487a3648515c9aa6fa89e31f2414eccfdbc"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/ed4524c87249edc3104f6bb28ab11325bed3d536"
    }
  ],
  "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 seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • 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.