Skip to content
Heist/ feed
Back to feed
MediumFix available

regulator: dummy: force synchronous probing

Type: advisorySources: OSV

In the Linux kernel, the following vulnerability has been resolved: regulator: dummy: force synchronous probing Sometimes I get a NULL pointer dereference at boot time in kobject_get() with the following call stack: anatop_regulator_probe() devm_regulator_register() regulator_register() regulator_resolve_supply() kobject_get() By placing some extra BUG_ON() statements I could verify that this is raised because probing of the 'dummy' regulator driver is not completed ('dummy_regulator_rdev' is still NULL). In the JTAG debugger I can see that dummy_regulator_probe() and anatop_regulator_probe() can be run by different kernel threads (kworker/u4:*). I haven't further investigated whether this can be changed or if there are other possibilities to force synchronization between these two probe routines. On the other hand I don't expect much boot time penalty by probing the 'dummy' regulator synchronously.

Products
Kernel
Affected versions
Not specified
Fixed versions
6.12.21, 6.13.9, 6.6.85
CVEs
CVE-2025-22009
Confirmed fixed CVEs
Not specified
Updated in this feed
3 Nov 2026, 13:39 UTC · Revision 1

Source evidence

regulator: dummy: force synchronous probing

core-osv · Original source

Published 8 Apr 2025, 08:17 UTC

In the Linux kernel, the following vulnerability has been resolved: regulator: dummy: force synchronous probing Sometimes I get a NULL pointer dereference at boot time in kobject_get() with the following call stack: anatop_regulator_probe() devm_regulator_register() regulator_register() regulator_resolve_supply() kobject_get() By placing some extra BUG_ON() statements I could verify that this is raised because probing of the 'dummy' regulator driver is not completed ('dummy_regulator_rdev' is still NULL). In the JTAG debugger I can see that dummy_regulator_probe() and anatop_regulator_probe() can be run by different kernel threads (kworker/u4:*). I haven't further investigated whether this can be changed or if there are other possibilities to force synchronization between these two probe routines. On the other hand I don't expect much boot time penalty by probing the 'dummy' regulator synchronously.

osv:CVE-2025-22009

Kernel

Fixed versions: 6.6.85, 6.12.21, 6.13.9

Complete source record
{
  "id": "f641e1d755f10f426ca4b27edb5943152b225177a79f7c427f54bdb5cab8aac7",
  "url": "https://osv.dev/vulnerability/CVE-2025-22009",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "regulator: dummy: force synchronous probing",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: regulator: dummy: force synchronous probing Sometimes I get a NULL pointer dereference at boot time in kobject_get() with the following call stack: anatop_regulator_probe() devm_regulator_register() regulator_register() regulator_resolve_supply() kobject_get() By placing some extra BUG_ON() statements I could verify that this is raised because probing of the 'dummy' regulator driver is not completed ('dummy_regulator_rdev' is still NULL). In the JTAG debugger I can see that dummy_regulator_probe() and anatop_regulator_probe() can be run by different kernel threads (kworker/u4:*). I haven't further investigated whether this can be changed or if there are other possibilities to force synchronization between these two probe routines. On the other hand I don't expect much boot time penalty by probing the 'dummy' regulator synchronously.",
    "evidence": "osv:CVE-2025-22009",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.6.85",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.12.21",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.13.9",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "medium",
    "structured": {
      "id": "CVE-2025-22009",
      "aliases": [
        "CVE-2025-22009"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "259b93b21a9ffe5117af4dfb5505437e463c6a5a"
                },
                {
                  "fixed": "e26f24ca4fb940b15e092796c5993142a2558bd9"
                },
                {
                  "fixed": "d3b83a1442a09b145006eb4294b1a963c5345c9c"
                },
                {
                  "fixed": "5ade367b56c3947c990598df92395ce737bee872"
                },
                {
                  "fixed": "8619909b38eeebd3e60910158d7d68441fc954e9"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-22009.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.4.0"
                },
                {
                  "fixed": "6.6.85"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.7.0"
                },
                {
                  "fixed": "6.12.21"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.13.0"
                },
                {
                  "fixed": "6.13.9"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-22009.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:29.374641929Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/5ade367b56c3947c990598df92395ce737bee872",
        "https://git.kernel.org/stable/c/8619909b38eeebd3e60910158d7d68441fc954e9",
        "https://git.kernel.org/stable/c/d3b83a1442a09b145006eb4294b1a963c5345c9c",
        "https://git.kernel.org/stable/c/e26f24ca4fb940b15e092796c5993142a2558bd9",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/22xxx/CVE-2025-22009.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2025-22009",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/22xxx/CVE-2025-22009.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2025-22009",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 496003,
  "published_at": "2025-04-08T08:17:59.84+00:00"
}