fkie_cve-2024-57891
Vulnerability from fkie_nvd
Published
2025-01-15 13:15
Modified
2025-01-15 13:15
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: sched_ext: Fix invalid irq restore in scx_ops_bypass() While adding outer irqsave/restore locking, 0e7ffff1b811 ("scx: Fix raciness in scx_ops_bypass()") forgot to convert an inner rq_unlock_irqrestore() to rq_unlock() which could re-enable IRQ prematurely leading to the following warning: raw_local_irq_restore() called with IRQs enabled WARNING: CPU: 1 PID: 96 at kernel/locking/irqflag-debug.c:10 warn_bogus_irq_restore+0x30/0x40 ... Sched_ext: create_dsq (enabling) pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : warn_bogus_irq_restore+0x30/0x40 lr : warn_bogus_irq_restore+0x30/0x40 ... Call trace: warn_bogus_irq_restore+0x30/0x40 (P) warn_bogus_irq_restore+0x30/0x40 (L) scx_ops_bypass+0x224/0x3b8 scx_ops_enable.isra.0+0x2c8/0xaa8 bpf_scx_reg+0x18/0x30 ... irq event stamp: 33739 hardirqs last enabled at (33739): [<ffff8000800b699c>] scx_ops_bypass+0x174/0x3b8 hardirqs last disabled at (33738): [<ffff800080d48ad4>] _raw_spin_lock_irqsave+0xb4/0xd8 Drop the stray _irqrestore().
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/18b2093f4598d8ee67a8153badc93f0fa7686b8a
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/786362ce60d79967875f43e0ba55ad7a5376c133
Impacted products
Vendor Product Version


To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsched_ext: Fix invalid irq restore in scx_ops_bypass()\n\nWhile adding outer irqsave/restore locking, 0e7ffff1b811 (\"scx: Fix raciness\nin scx_ops_bypass()\") forgot to convert an inner rq_unlock_irqrestore() to\nrq_unlock() which could re-enable IRQ prematurely leading to the following\nwarning:\n\n  raw_local_irq_restore() called with IRQs enabled\n  WARNING: CPU: 1 PID: 96 at kernel/locking/irqflag-debug.c:10 warn_bogus_irq_restore+0x30/0x40\n  ...\n  Sched_ext: create_dsq (enabling)\n  pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n  pc : warn_bogus_irq_restore+0x30/0x40\n  lr : warn_bogus_irq_restore+0x30/0x40\n  ...\n  Call trace:\n   warn_bogus_irq_restore+0x30/0x40 (P)\n   warn_bogus_irq_restore+0x30/0x40 (L)\n   scx_ops_bypass+0x224/0x3b8\n   scx_ops_enable.isra.0+0x2c8/0xaa8\n   bpf_scx_reg+0x18/0x30\n  ...\n  irq event stamp: 33739\n  hardirqs last  enabled at (33739): [\u003cffff8000800b699c\u003e] scx_ops_bypass+0x174/0x3b8\n  hardirqs last disabled at (33738): [\u003cffff800080d48ad4\u003e] _raw_spin_lock_irqsave+0xb4/0xd8\n\nDrop the stray _irqrestore()."
    },
    {
      "lang": "es",
      "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: sched_ext: Arreglar restauraci\u00f3n de irq no v\u00e1lida en scx_ops_bypass() Al agregar el bloqueo de irqsave/restore externo, 0e7ffff1b811 (\"scx: Arreglar la agresividad en scx_ops_bypass()\") olvid\u00f3 convertir un rq_unlock_irqrestore() interno en rq_unlock() que podr\u00eda volver a habilitar IRQ prematuramente, lo que genera la siguiente advertencia: raw_local_irq_restore() llamado con IRQ habilitados ADVERTENCIA: CPU: 1 PID: 96 en kernel/locking/irqflag-debug.c:10 warn_bogus_irq_restore+0x30/0x40 ... Sched_ext: create_dsq (habilitando) pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : warn_bogus_irq_restore+0x30/0x40 lr : warn_bogus_irq_restore+0x30/0x40 ... Rastreo de llamadas: warn_bogus_irq_restore+0x30/0x40 (P) warn_bogus_irq_restore+0x30/0x40 (L) scx_ops_bypass+0x224/0x3b8 scx_ops_enable.isra.0+0x2c8/0xaa8 bpf_scx_reg+0x18/0x30 ... marca de evento irq: 33739 hardirqs habilitados por \u00faltima vez en (33739): [] scx_ops_bypass+0x174/0x3b8 hardirqs deshabilitados por \u00faltima vez en (33738): [] _raw_spin_lock_irqsave+0xb4/0xd8 Elimina el _irqrestore() perdido."
    }
  ],
  "id": "CVE-2024-57891",
  "lastModified": "2025-01-15T13:15:13.590",
  "metrics": {},
  "published": "2025-01-15T13:15:13.590",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/18b2093f4598d8ee67a8153badc93f0fa7686b8a"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/786362ce60d79967875f43e0ba55ad7a5376c133"
    }
  ],
  "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.