CVE-2025-21657 (GCVE-0-2025-21657)
Vulnerability from cvelistv5
Published
2025-01-21 12:18
Modified
2025-05-04 07:18
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: sched_ext: Replace rq_lock() to raw_spin_rq_lock() in scx_ops_bypass() scx_ops_bypass() iterates all CPUs to re-enqueue all the scx tasks. For each CPU, it acquires a lock using rq_lock() regardless of whether a CPU is offline or the CPU is currently running a task in a higher scheduler class (e.g., deadline). The rq_lock() is supposed to be used for online CPUs, and the use of rq_lock() may trigger an unnecessary warning in rq_pin_lock(). Therefore, replace rq_lock() to raw_spin_rq_lock() in scx_ops_bypass(). Without this change, we observe the following warning: ===== START ===== [ 6.615205] rq->balance_callback && rq->balance_callback != &balance_push_callback [ 6.615208] WARNING: CPU: 2 PID: 0 at kernel/sched/sched.h:1730 __schedule+0x1130/0x1c90 ===== END =====
Impacted products
Vendor Product Version
Linux Linux Version: 0e7ffff1b8117b05635c87d3c9099f6aa9c9b689
Version: 0e7ffff1b8117b05635c87d3c9099f6aa9c9b689
Create a notification for this product.
Show details on NVD website


{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "kernel/sched/ext.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "d9e446dd63cee7161717a6a8414ba9c6435af764",
              "status": "affected",
              "version": "0e7ffff1b8117b05635c87d3c9099f6aa9c9b689",
              "versionType": "git"
            },
            {
              "lessThan": "6268d5bc10354fc2ab8d44a0cd3b042d49a0417e",
              "status": "affected",
              "version": "0e7ffff1b8117b05635c87d3c9099f6aa9c9b689",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "kernel/sched/ext.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.12"
            },
            {
              "lessThan": "6.12",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.10",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.13",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.10",
                  "versionStartIncluding": "6.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.13",
                  "versionStartIncluding": "6.12",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsched_ext: Replace rq_lock() to raw_spin_rq_lock() in scx_ops_bypass()\n\nscx_ops_bypass() iterates all CPUs to re-enqueue all the scx tasks.\nFor each CPU, it acquires a lock using rq_lock() regardless of whether\na CPU is offline or the CPU is currently running a task in a higher\nscheduler class (e.g., deadline). The rq_lock() is supposed to be used\nfor online CPUs, and the use of rq_lock() may trigger an unnecessary\nwarning in rq_pin_lock(). Therefore, replace rq_lock() to\nraw_spin_rq_lock() in scx_ops_bypass().\n\nWithout this change, we observe the following warning:\n\n===== START =====\n[    6.615205] rq-\u003ebalance_callback \u0026\u0026 rq-\u003ebalance_callback != \u0026balance_push_callback\n[    6.615208] WARNING: CPU: 2 PID: 0 at kernel/sched/sched.h:1730 __schedule+0x1130/0x1c90\n=====  END  ====="
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-05-04T07:18:22.917Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/d9e446dd63cee7161717a6a8414ba9c6435af764"
        },
        {
          "url": "https://git.kernel.org/stable/c/6268d5bc10354fc2ab8d44a0cd3b042d49a0417e"
        }
      ],
      "title": "sched_ext: Replace rq_lock() to raw_spin_rq_lock() in scx_ops_bypass()",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-21657",
    "datePublished": "2025-01-21T12:18:13.893Z",
    "dateReserved": "2024-12-29T08:45:45.731Z",
    "dateUpdated": "2025-05-04T07:18:22.917Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2025-21657\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-01-21T13:15:09.340\",\"lastModified\":\"2025-01-21T13:15:09.340\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nsched_ext: Replace rq_lock() to raw_spin_rq_lock() in scx_ops_bypass()\\n\\nscx_ops_bypass() iterates all CPUs to re-enqueue all the scx tasks.\\nFor each CPU, it acquires a lock using rq_lock() regardless of whether\\na CPU is offline or the CPU is currently running a task in a higher\\nscheduler class (e.g., deadline). The rq_lock() is supposed to be used\\nfor online CPUs, and the use of rq_lock() may trigger an unnecessary\\nwarning in rq_pin_lock(). Therefore, replace rq_lock() to\\nraw_spin_rq_lock() in scx_ops_bypass().\\n\\nWithout this change, we observe the following warning:\\n\\n===== START =====\\n[    6.615205] rq-\u003ebalance_callback \u0026\u0026 rq-\u003ebalance_callback != \u0026balance_push_callback\\n[    6.615208] WARNING: CPU: 2 PID: 0 at kernel/sched/sched.h:1730 __schedule+0x1130/0x1c90\\n=====  END  =====\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: sched_ext: Reemplace rq_lock() por raw_spin_rq_lock() en scx_ops_bypass() scx_ops_bypass() itera todas las CPU para volver a poner en cola todas las tareas de scx. Para cada CPU, adquiere un bloqueo mediante rq_lock() independientemente de si una CPU est\u00e1 fuera de l\u00ednea o si la CPU est\u00e1 ejecutando actualmente una tarea en una clase de programador superior (por ejemplo, fecha l\u00edmite). Se supone que rq_lock() se debe utilizar para CPU en l\u00ednea, y el uso de rq_lock() puede activar una advertencia innecesaria en rq_pin_lock(). Por lo tanto, reemplace rq_lock() por raw_spin_rq_lock() en scx_ops_bypass(). Sin este cambio, observamos la siguiente advertencia: ===== START ===== [ 6.615205] rq-\u0026gt;balance_callback \u0026amp;\u0026amp; rq-\u0026gt;balance_callback != \u0026amp;balance_push_callback [ 6.615208] ADVERTENCIA: CPU: 2 PID: 0 en kernel/sched/sched.h:1730 __schedule+0x1130/0x1c90 ===== END ========== \"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/6268d5bc10354fc2ab8d44a0cd3b042d49a0417e\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/d9e446dd63cee7161717a6a8414ba9c6435af764\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.


Loading…

Loading…