FKIE_CVE-2025-21803

Vulnerability from fkie_nvd - Published: 2025-02-27 20:16 - Updated: 2026-06-17 08:44
Severity
5.5 (Medium) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Summary
In the Linux kernel, the following vulnerability has been resolved: LoongArch: Fix warnings during S3 suspend The enable_gpe_wakeup() function calls acpi_enable_all_wakeup_gpes(), and the later one may call the preempt_schedule_common() function, resulting in a thread switch and causing the CPU to be in an interrupt enabled state after the enable_gpe_wakeup() function returns, leading to the warnings as follow. [ C0] WARNING: ... at kernel/time/timekeeping.c:845 ktime_get+0xbc/0xc8 [ C0] ... [ C0] Call Trace: [ C0] [<90000000002243b4>] show_stack+0x64/0x188 [ C0] [<900000000164673c>] dump_stack_lvl+0x60/0x88 [ C0] [<90000000002687e4>] __warn+0x8c/0x148 [ C0] [<90000000015e9978>] report_bug+0x1c0/0x2b0 [ C0] [<90000000016478e4>] do_bp+0x204/0x3b8 [ C0] [<90000000025b1924>] exception_handlers+0x1924/0x10000 [ C0] [<9000000000343bbc>] ktime_get+0xbc/0xc8 [ C0] [<9000000000354c08>] tick_sched_timer+0x30/0xb0 [ C0] [<90000000003408e0>] __hrtimer_run_queues+0x160/0x378 [ C0] [<9000000000341f14>] hrtimer_interrupt+0x144/0x388 [ C0] [<9000000000228348>] constant_timer_interrupt+0x38/0x48 [ C0] [<90000000002feba4>] __handle_irq_event_percpu+0x64/0x1e8 [ C0] [<90000000002fed48>] handle_irq_event_percpu+0x20/0x80 [ C0] [<9000000000306b9c>] handle_percpu_irq+0x5c/0x98 [ C0] [<90000000002fd4a0>] generic_handle_domain_irq+0x30/0x48 [ C0] [<9000000000d0c7b0>] handle_cpu_irq+0x70/0xa8 [ C0] [<9000000001646b30>] handle_loongarch_irq+0x30/0x48 [ C0] [<9000000001646bc8>] do_vint+0x80/0xe0 [ C0] [<90000000002aea1c>] finish_task_switch.isra.0+0x8c/0x2a8 [ C0] [<900000000164e34c>] __schedule+0x314/0xa48 [ C0] [<900000000164ead8>] schedule+0x58/0xf0 [ C0] [<9000000000294a2c>] worker_thread+0x224/0x498 [ C0] [<900000000029d2f0>] kthread+0xf8/0x108 [ C0] [<9000000000221f28>] ret_from_kernel_thread+0xc/0xa4 [ C0] [ C0] ---[ end trace 0000000000000000 ]--- The root cause is acpi_enable_all_wakeup_gpes() uses a mutex to protect acpi_hw_enable_all_wakeup_gpes(), and acpi_ut_acquire_mutex() may cause a thread switch. Since there is no longer concurrent execution during loongarch_acpi_suspend(), we can call acpi_hw_enable_all_wakeup_gpes() directly in enable_gpe_wakeup(). The solution is similar to commit 22db06337f590d01 ("ACPI: sleep: Avoid breaking S3 wakeup due to might_sleep()").
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/194d26a5a43c26dc98a9b4e2c1d521dcb84dd1bfPatch
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/26c0a2d93af55d30a46d5f45d3e9c42cde730168Patch
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/8682a71a7f6de7c683f31b4334b04e19685a05f9Patch
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/d49ab6857d98266010f3446c9c2063014db5b654Patch
Impacted products
Vendor Product Version
linux linux_kernel *
linux linux_kernel *
linux linux_kernel *
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "arch/loongarch/power/platform.c",
            "drivers/acpi/acpica/achware.h",
            "include/acpi/acpixf.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "d49ab6857d98266010f3446c9c2063014db5b654",
              "status": "affected",
              "version": "366bb35a8e48198cefcd3484ac6b2374d1347873",
              "versionType": "git"
            },
            {
              "lessThan": "194d26a5a43c26dc98a9b4e2c1d521dcb84dd1bf",
              "status": "affected",
              "version": "366bb35a8e48198cefcd3484ac6b2374d1347873",
              "versionType": "git"
            },
            {
              "lessThan": "8682a71a7f6de7c683f31b4334b04e19685a05f9",
              "status": "affected",
              "version": "366bb35a8e48198cefcd3484ac6b2374d1347873",
              "versionType": "git"
            },
            {
              "lessThan": "26c0a2d93af55d30a46d5f45d3e9c42cde730168",
              "status": "affected",
              "version": "366bb35a8e48198cefcd3484ac6b2374d1347873",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "arch/loongarch/power/platform.c",
            "drivers/acpi/acpica/achware.h",
            "include/acpi/acpixf.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.2"
            },
            {
              "lessThan": "6.2",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.76",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.13",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.13.*",
              "status": "unaffected",
              "version": "6.13.2",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.14",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "A6D70701-9CB6-4222-A957-00A419878993",
              "versionEndExcluding": "6.6.76",
              "versionStartIncluding": "6.2",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "2897389C-A8C3-4D69-90F2-E701B3D66373",
              "versionEndExcluding": "6.12.13",
              "versionStartIncluding": "6.7",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "6D4116B1-1BFD-4F23-BA84-169CC05FC5A3",
              "versionEndExcluding": "6.13.2",
              "versionStartIncluding": "6.13",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: Fix warnings during S3 suspend\n\nThe enable_gpe_wakeup() function calls acpi_enable_all_wakeup_gpes(),\nand the later one may call the preempt_schedule_common() function,\nresulting in a thread switch and causing the CPU to be in an interrupt\nenabled state after the enable_gpe_wakeup() function returns, leading\nto the warnings as follow.\n\n[ C0] WARNING: ... at kernel/time/timekeeping.c:845 ktime_get+0xbc/0xc8\n[ C0]          ...\n[ C0] Call Trace:\n[ C0] [\u003c90000000002243b4\u003e] show_stack+0x64/0x188\n[ C0] [\u003c900000000164673c\u003e] dump_stack_lvl+0x60/0x88\n[ C0] [\u003c90000000002687e4\u003e] __warn+0x8c/0x148\n[ C0] [\u003c90000000015e9978\u003e] report_bug+0x1c0/0x2b0\n[ C0] [\u003c90000000016478e4\u003e] do_bp+0x204/0x3b8\n[ C0] [\u003c90000000025b1924\u003e] exception_handlers+0x1924/0x10000\n[ C0] [\u003c9000000000343bbc\u003e] ktime_get+0xbc/0xc8\n[ C0] [\u003c9000000000354c08\u003e] tick_sched_timer+0x30/0xb0\n[ C0] [\u003c90000000003408e0\u003e] __hrtimer_run_queues+0x160/0x378\n[ C0] [\u003c9000000000341f14\u003e] hrtimer_interrupt+0x144/0x388\n[ C0] [\u003c9000000000228348\u003e] constant_timer_interrupt+0x38/0x48\n[ C0] [\u003c90000000002feba4\u003e] __handle_irq_event_percpu+0x64/0x1e8\n[ C0] [\u003c90000000002fed48\u003e] handle_irq_event_percpu+0x20/0x80\n[ C0] [\u003c9000000000306b9c\u003e] handle_percpu_irq+0x5c/0x98\n[ C0] [\u003c90000000002fd4a0\u003e] generic_handle_domain_irq+0x30/0x48\n[ C0] [\u003c9000000000d0c7b0\u003e] handle_cpu_irq+0x70/0xa8\n[ C0] [\u003c9000000001646b30\u003e] handle_loongarch_irq+0x30/0x48\n[ C0] [\u003c9000000001646bc8\u003e] do_vint+0x80/0xe0\n[ C0] [\u003c90000000002aea1c\u003e] finish_task_switch.isra.0+0x8c/0x2a8\n[ C0] [\u003c900000000164e34c\u003e] __schedule+0x314/0xa48\n[ C0] [\u003c900000000164ead8\u003e] schedule+0x58/0xf0\n[ C0] [\u003c9000000000294a2c\u003e] worker_thread+0x224/0x498\n[ C0] [\u003c900000000029d2f0\u003e] kthread+0xf8/0x108\n[ C0] [\u003c9000000000221f28\u003e] ret_from_kernel_thread+0xc/0xa4\n[ C0]\n[ C0] ---[ end trace 0000000000000000 ]---\n\nThe root cause is acpi_enable_all_wakeup_gpes() uses a mutex to protect\nacpi_hw_enable_all_wakeup_gpes(), and acpi_ut_acquire_mutex() may cause\na thread switch. Since there is no longer concurrent execution during\nloongarch_acpi_suspend(), we can call acpi_hw_enable_all_wakeup_gpes()\ndirectly in enable_gpe_wakeup().\n\nThe solution is similar to commit 22db06337f590d01 (\"ACPI: sleep: Avoid\nbreaking S3 wakeup due to might_sleep()\")."
    },
    {
      "lang": "es",
      "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: LoongArch: Se corrigen advertencias durante la suspensi\u00f3n de S3 La funci\u00f3n enable_gpe_wakeup() llama a acpi_enable_all_wakeup_gpes(), y la \u00faltima puede llamar a la funci\u00f3n preempt_schedule_common(), lo que da como resultado un cambio de hilo y hace que la CPU est\u00e9 en un estado de interrupci\u00f3n habilitada despu\u00e9s de que la funci\u00f3n enable_gpe_wakeup() regrese, lo que genera las advertencias siguientes. [ C0] ADVERTENCIA: ... en kernel/time/timekeeping.c:845 ktime_get+0xbc/0xc8 [ C0] ... [ C0] Call Trace: [ C0] [\u0026lt;90000000002243b4\u0026gt;] show_stack+0x64/0x188 [ C0] [\u0026lt;900000000164673c\u0026gt;] dump_stack_lvl+0x60/0x88 [ C0] [\u0026lt;90000000002687e4\u0026gt;] __warn+0x8c/0x148 [ C0] [\u0026lt;90000000015e9978\u0026gt;] report_bug+0x1c0/0x2b0 [ C0] [\u0026lt;90000000016478e4\u0026gt;] do_bp+0x204/0x3b8 [ C0] [\u0026lt;90000000025b1924\u0026gt;] exception_handlers+0x1924/0x10000 [ C0] [\u0026lt;9000000000343bbc\u0026gt;] ktime_get+0xbc/0xc8 [ C0] [\u0026lt;9000000000354c08\u0026gt;] tick_sched_timer+0x30/0xb0 [ C0] [\u0026lt;90000000003408e0\u0026gt;] __hrtimer_run_queues+0x160/0x378 [ C0] [\u0026lt;9000000000341f14\u0026gt;] hrtimer_interrupt+0x144/0x388 [ C0] [\u0026lt;9000000000228348\u0026gt;] constant_timer_interrupt+0x38/0x48 [ C0] [\u0026lt;90000000002feba4\u0026gt;] __handle_irq_event_percpu+0x64/0x1e8 [ C0] [\u0026lt;90000000002fed48\u0026gt;] handle_irq_event_percpu+0x20/0x80 [ C0] [\u0026lt;9000000000306b9c\u0026gt;] handle_percpu_irq+0x5c/0x98 [ C0] [\u0026lt;90000000002fd4a0\u0026gt;] generic_handle_domain_irq+0x30/0x48 [ C0] [\u0026lt;9000000000d0c7b0\u0026gt;] handle_cpu_irq+0x70/0xa8 [ C0] [\u0026lt;9000000001646b30\u0026gt;] handle_loongarch_irq+0x30/0x48 [ C0] [\u0026lt;9000000001646bc8\u0026gt;] do_vint+0x80/0xe0 [ C0] [\u0026lt;90000000002aea1c\u0026gt;] finish_task_switch.isra.0+0x8c/0x2a8 [ C0] [\u0026lt;900000000164e34c\u0026gt;] __schedule+0x314/0xa48 [ C0] [\u0026lt;900000000164ead8\u0026gt;] schedule+0x58/0xf0 [ C0] [\u0026lt;9000000000294a2c\u0026gt;] worker_thread+0x224/0x498 [ C0] [\u0026lt;900000000029d2f0\u0026gt;] kthread+0xf8/0x108 [ C0] [\u0026lt;9000000000221f28\u0026gt;] ret_from_kernel_thread+0xc/0xa4 [ C0] [ C0] ---[ end trace 0000000000000000 ]--- The root cause is acpi_enable_all_wakeup_gpes() uses a mutex to protect acpi_hw_enable_all_wakeup_gpes(), and acpi_ut_acquire_mutex() may cause a thread switch. Dado que ya no hay ejecuci\u00f3n simult\u00e1nea durante loongarch_acpi_suspend(), podemos llamar a acpi_hw_enable_all_wakeup_gpes() directamente en enable_gpe_wakeup(). La soluci\u00f3n es similar a el commit 22db06337f590d01 (\"ACPI: sleep: evitar interrumpir la activaci\u00f3n de S3 debido a might_sleep()\")."
    }
  ],
  "id": "CVE-2025-21803",
  "lastModified": "2026-06-17T08:44:19.080",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "LOCAL",
          "availabilityImpact": "HIGH",
          "baseScore": 5.5,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "NONE",
          "integrityImpact": "NONE",
          "privilegesRequired": "LOW",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 1.8,
        "impactScore": 3.6,
        "source": "nvd@nist.gov",
        "type": "Primary"
      }
    ]
  },
  "published": "2025-02-27T20:16:02.937",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "tags": [
        "Patch"
      ],
      "url": "https://git.kernel.org/stable/c/194d26a5a43c26dc98a9b4e2c1d521dcb84dd1bf"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "tags": [
        "Patch"
      ],
      "url": "https://git.kernel.org/stable/c/26c0a2d93af55d30a46d5f45d3e9c42cde730168"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "tags": [
        "Patch"
      ],
      "url": "https://git.kernel.org/stable/c/8682a71a7f6de7c683f31b4334b04e19685a05f9"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "tags": [
        "Patch"
      ],
      "url": "https://git.kernel.org/stable/c/d49ab6857d98266010f3446c9c2063014db5b654"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "NVD-CWE-noinfo"
        }
      ],
      "source": "nvd@nist.gov",
      "type": "Primary"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.