CVE-2025-21816 (GCVE-0-2025-21816)
Vulnerability from cvelistv5
Published
2025-02-27 20:04
Modified
2025-06-04 12:57
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: hrtimers: Force migrate away hrtimers queued after CPUHP_AP_HRTIMERS_DYING hrtimers are migrated away from the dying CPU to any online target at the CPUHP_AP_HRTIMERS_DYING stage in order not to delay bandwidth timers handling tasks involved in the CPU hotplug forward progress. However wakeups can still be performed by the outgoing CPU after CPUHP_AP_HRTIMERS_DYING. Those can result again in bandwidth timers being armed. Depending on several considerations (crystal ball power management based election, earliest timer already enqueued, timer migration enabled or not), the target may eventually be the current CPU even if offline. If that happens, the timer is eventually ignored. The most notable example is RCU which had to deal with each and every of those wake-ups by deferring them to an online CPU, along with related workarounds: _ e787644caf76 (rcu: Defer RCU kthreads wakeup when CPU is dying) _ 9139f93209d1 (rcu/nocb: Fix RT throttling hrtimer armed from offline CPU) _ f7345ccc62a4 (rcu/nocb: Fix rcuog wake-up from offline softirq) The problem isn't confined to RCU though as the stop machine kthread (which runs CPUHP_AP_HRTIMERS_DYING) reports its completion at the end of its work through cpu_stop_signal_done() and performs a wake up that eventually arms the deadline server timer: WARNING: CPU: 94 PID: 588 at kernel/time/hrtimer.c:1086 hrtimer_start_range_ns+0x289/0x2d0 CPU: 94 UID: 0 PID: 588 Comm: migration/94 Not tainted Stopper: multi_cpu_stop+0x0/0x120 <- stop_machine_cpuslocked+0x66/0xc0 RIP: 0010:hrtimer_start_range_ns+0x289/0x2d0 Call Trace: <TASK> start_dl_timer enqueue_dl_entity dl_server_start enqueue_task_fair enqueue_task ttwu_do_activate try_to_wake_up complete cpu_stopper_thread Instead of providing yet another bandaid to work around the situation, fix it in the hrtimers infrastructure instead: always migrate away a timer to an online target whenever it is enqueued from an offline CPU. This will also allow to revert all the above RCU disgraceful hacks.
References
Impacted products
Vendor Product Version
Linux Linux Version: 75b5016ce325f1ef9c63e5398a1064cf8a7a7354
Version: 53f408cad05bb987af860af22f4151e5a18e6ee8
Version: 5c0930ccaad5a74d74e8b18b648c5eb21ed2fe94
Version: 5c0930ccaad5a74d74e8b18b648c5eb21ed2fe94
Version: 5c0930ccaad5a74d74e8b18b648c5eb21ed2fe94
Version: 9a2fc41acb69dd4e2a58d0c04346c3333c2341fc
Version: 54d0d83a53508d687fd4a225f8aa1f18559562d0
Version: 7f4c89400d2997939f6971c7981cc780a219e36b
Version: 6fcbcc6c8e52650749692c7613cbe71bf601670d
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "include/linux/hrtimer_defs.h",
            "kernel/time/hrtimer.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "82ac6adbbb2aad14548a71d5e2e37f4964a15e38",
              "status": "affected",
              "version": "75b5016ce325f1ef9c63e5398a1064cf8a7a7354",
              "versionType": "git"
            },
            {
              "lessThan": "63815bef47ec25f5a125019ca480882481ee1553",
              "status": "affected",
              "version": "53f408cad05bb987af860af22f4151e5a18e6ee8",
              "versionType": "git"
            },
            {
              "lessThan": "e456a88bddae4030ba962447bb84be6669f2a0c1",
              "status": "affected",
              "version": "5c0930ccaad5a74d74e8b18b648c5eb21ed2fe94",
              "versionType": "git"
            },
            {
              "lessThan": "2aecec58e9040ce3d2694707889f9914a2374955",
              "status": "affected",
              "version": "5c0930ccaad5a74d74e8b18b648c5eb21ed2fe94",
              "versionType": "git"
            },
            {
              "lessThan": "53dac345395c0d2493cbc2f4c85fe38aef5b63f5",
              "status": "affected",
              "version": "5c0930ccaad5a74d74e8b18b648c5eb21ed2fe94",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "9a2fc41acb69dd4e2a58d0c04346c3333c2341fc",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "54d0d83a53508d687fd4a225f8aa1f18559562d0",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "7f4c89400d2997939f6971c7981cc780a219e36b",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "6fcbcc6c8e52650749692c7613cbe71bf601670d",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "include/linux/hrtimer_defs.h",
            "kernel/time/hrtimer.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.7"
            },
            {
              "lessThan": "6.7",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.141",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.93",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.14",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.13.*",
              "status": "unaffected",
              "version": "6.13.3",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.14",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.141",
                  "versionStartIncluding": "6.1.68",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.93",
                  "versionStartIncluding": "6.6.7",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.14",
                  "versionStartIncluding": "6.7",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.13.3",
                  "versionStartIncluding": "6.7",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.14",
                  "versionStartIncluding": "6.7",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionStartIncluding": "4.19.302",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionStartIncluding": "5.4.264",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionStartIncluding": "5.10.204",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionStartIncluding": "5.15.143",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nhrtimers: Force migrate away hrtimers queued after CPUHP_AP_HRTIMERS_DYING\n\nhrtimers are migrated away from the dying CPU to any online target at\nthe CPUHP_AP_HRTIMERS_DYING stage in order not to delay bandwidth timers\nhandling tasks involved in the CPU hotplug forward progress.\n\nHowever wakeups can still be performed by the outgoing CPU after\nCPUHP_AP_HRTIMERS_DYING. Those can result again in bandwidth timers being\narmed. Depending on several considerations (crystal ball power management\nbased election, earliest timer already enqueued, timer migration enabled or\nnot), the target may eventually be the current CPU even if offline. If that\nhappens, the timer is eventually ignored.\n\nThe most notable example is RCU which had to deal with each and every of\nthose wake-ups by deferring them to an online CPU, along with related\nworkarounds:\n\n_ e787644caf76 (rcu: Defer RCU kthreads wakeup when CPU is dying)\n_ 9139f93209d1 (rcu/nocb: Fix RT throttling hrtimer armed from offline CPU)\n_ f7345ccc62a4 (rcu/nocb: Fix rcuog wake-up from offline softirq)\n\nThe problem isn\u0027t confined to RCU though as the stop machine kthread\n(which runs CPUHP_AP_HRTIMERS_DYING) reports its completion at the end\nof its work through cpu_stop_signal_done() and performs a wake up that\neventually arms the deadline server timer:\n\n   WARNING: CPU: 94 PID: 588 at kernel/time/hrtimer.c:1086 hrtimer_start_range_ns+0x289/0x2d0\n   CPU: 94 UID: 0 PID: 588 Comm: migration/94 Not tainted\n   Stopper: multi_cpu_stop+0x0/0x120 \u003c- stop_machine_cpuslocked+0x66/0xc0\n   RIP: 0010:hrtimer_start_range_ns+0x289/0x2d0\n   Call Trace:\n   \u003cTASK\u003e\n     start_dl_timer\n     enqueue_dl_entity\n     dl_server_start\n     enqueue_task_fair\n     enqueue_task\n     ttwu_do_activate\n     try_to_wake_up\n     complete\n     cpu_stopper_thread\n\nInstead of providing yet another bandaid to work around the situation, fix\nit in the hrtimers infrastructure instead: always migrate away a timer to\nan online target whenever it is enqueued from an offline CPU.\n\nThis will also allow to revert all the above RCU disgraceful hacks."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-06-04T12:57:22.282Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/82ac6adbbb2aad14548a71d5e2e37f4964a15e38"
        },
        {
          "url": "https://git.kernel.org/stable/c/63815bef47ec25f5a125019ca480882481ee1553"
        },
        {
          "url": "https://git.kernel.org/stable/c/e456a88bddae4030ba962447bb84be6669f2a0c1"
        },
        {
          "url": "https://git.kernel.org/stable/c/2aecec58e9040ce3d2694707889f9914a2374955"
        },
        {
          "url": "https://git.kernel.org/stable/c/53dac345395c0d2493cbc2f4c85fe38aef5b63f5"
        }
      ],
      "title": "hrtimers: Force migrate away hrtimers queued after CPUHP_AP_HRTIMERS_DYING",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-21816",
    "datePublished": "2025-02-27T20:04:15.356Z",
    "dateReserved": "2024-12-29T08:45:45.774Z",
    "dateUpdated": "2025-06-04T12:57:22.282Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2025-21816\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-02-27T20:16:04.150\",\"lastModified\":\"2025-06-04T13:15:25.773\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nhrtimers: Force migrate away hrtimers queued after CPUHP_AP_HRTIMERS_DYING\\n\\nhrtimers are migrated away from the dying CPU to any online target at\\nthe CPUHP_AP_HRTIMERS_DYING stage in order not to delay bandwidth timers\\nhandling tasks involved in the CPU hotplug forward progress.\\n\\nHowever wakeups can still be performed by the outgoing CPU after\\nCPUHP_AP_HRTIMERS_DYING. Those can result again in bandwidth timers being\\narmed. Depending on several considerations (crystal ball power management\\nbased election, earliest timer already enqueued, timer migration enabled or\\nnot), the target may eventually be the current CPU even if offline. If that\\nhappens, the timer is eventually ignored.\\n\\nThe most notable example is RCU which had to deal with each and every of\\nthose wake-ups by deferring them to an online CPU, along with related\\nworkarounds:\\n\\n_ e787644caf76 (rcu: Defer RCU kthreads wakeup when CPU is dying)\\n_ 9139f93209d1 (rcu/nocb: Fix RT throttling hrtimer armed from offline CPU)\\n_ f7345ccc62a4 (rcu/nocb: Fix rcuog wake-up from offline softirq)\\n\\nThe problem isn\u0027t confined to RCU though as the stop machine kthread\\n(which runs CPUHP_AP_HRTIMERS_DYING) reports its completion at the end\\nof its work through cpu_stop_signal_done() and performs a wake up that\\neventually arms the deadline server timer:\\n\\n   WARNING: CPU: 94 PID: 588 at kernel/time/hrtimer.c:1086 hrtimer_start_range_ns+0x289/0x2d0\\n   CPU: 94 UID: 0 PID: 588 Comm: migration/94 Not tainted\\n   Stopper: multi_cpu_stop+0x0/0x120 \u003c- stop_machine_cpuslocked+0x66/0xc0\\n   RIP: 0010:hrtimer_start_range_ns+0x289/0x2d0\\n   Call Trace:\\n   \u003cTASK\u003e\\n     start_dl_timer\\n     enqueue_dl_entity\\n     dl_server_start\\n     enqueue_task_fair\\n     enqueue_task\\n     ttwu_do_activate\\n     try_to_wake_up\\n     complete\\n     cpu_stopper_thread\\n\\nInstead of providing yet another bandaid to work around the situation, fix\\nit in the hrtimers infrastructure instead: always migrate away a timer to\\nan online target whenever it is enqueued from an offline CPU.\\n\\nThis will also allow to revert all the above RCU disgraceful hacks.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: hrtimers: fuerza la migraci\u00f3n de los hrtimers en cola despu\u00e9s de CPUHP_AP_HRTIMERS_DYING. Los hrtimers se migran desde la CPU que se est\u00e1 muriendo a cualquier destino en l\u00ednea en la etapa CPUHP_AP_HRTIMERS_DYING para no retrasar las tareas de gesti\u00f3n de los temporizadores de ancho de banda involucradas en el progreso de avance de la conexi\u00f3n en caliente de la CPU. Sin embargo, las reactivaciones a\u00fan pueden ser realizadas por la CPU saliente despu\u00e9s de CPUHP_AP_HRTIMERS_DYING. Esto puede dar como resultado nuevamente que los temporizadores de ancho de banda se activen. Dependiendo de varias consideraciones (elecci\u00f3n basada en administraci\u00f3n de energ\u00eda de Crystal Ball, temporizador m\u00e1s antiguo ya en cola, migraci\u00f3n de temporizador habilitada o no), el destino puede eventualmente ser la CPU actual incluso si est\u00e1 fuera de l\u00ednea. Si eso sucede, el temporizador eventualmente se ignora. El ejemplo m\u00e1s notable es RCU, que tuvo que lidiar con todos y cada uno de esos despertares difiri\u00e9ndolos a una CPU en l\u00ednea, junto con workarounds relacionados: _ e787644caf76 (rcu: Diferir el despertar de kthreads de RCU cuando la CPU est\u00e1 muriendo) _ 9139f93209d1 (rcu/nocb: Reparar la limitaci\u00f3n de RT de hrtimer armado desde una CPU fuera de l\u00ednea) _ f7345ccc62a4 (rcu/nocb: Reparar el despertar de rcuog desde softirq fuera de l\u00ednea) El problema no se limita a RCU, ya que el kthread de la m\u00e1quina de detenci\u00f3n (que ejecuta CPUHP_AP_HRTIMERS_DYING) informa su finalizaci\u00f3n al final de su trabajo a trav\u00e9s de cpu_stop_signal_done() y realiza un despertar que eventualmente arma el temporizador del servidor de fecha l\u00edmite: ADVERTENCIA: CPU: 94 PID: 588 en kernel/time/hrtimer.c:1086 hrtimer_start_range_ns+0x289/0x2d0 CPU: 94 UID: 0 PID: 588 Comm: immigration/94 No contaminado Detenedor: multi_cpu_stop+0x0/0x120 \u0026lt;- stop_machine_cpuslocked+0x66/0xc0 RIP: 0010:hrtimer_start_range_ns+0x289/0x2d0 Rastreo de llamadas:  start_dl_timer enqueue_dl_entity dl_server_start enqueue_task_fair enqueue_task ttwu_do_activate try_to_wake_up complete cpu_stopper_thread En lugar de proporcionar otro workaround para solucionar la situaci\u00f3n, corr\u00edjala en la infraestructura de hrtimers: siempre migre un temporizador a un destino en l\u00ednea cuando se ponga en cola desde una CPU fuera de l\u00ednea. Esto tambi\u00e9n permitir\u00e1 revertir todos los vergonzosos hackeos de RCU mencionados anteriormente.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/2aecec58e9040ce3d2694707889f9914a2374955\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/53dac345395c0d2493cbc2f4c85fe38aef5b63f5\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/63815bef47ec25f5a125019ca480882481ee1553\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/82ac6adbbb2aad14548a71d5e2e37f4964a15e38\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/e456a88bddae4030ba962447bb84be6669f2a0c1\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


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.