GHSA-XRC9-FQ2P-6MM2

Vulnerability from github – Published: 2026-05-06 12:30 – Updated: 2026-05-12 21:31
VLAI?
Details

In the Linux kernel, the following vulnerability has been resolved:

ACPI: processor: Update cpuidle driver check in __acpi_processor_start()

Commit 7a8c994cbb2d ("ACPI: processor: idle: Optimize ACPI idle driver registration") moved the ACPI idle driver registration to acpi_processor_driver_init() and acpi_processor_power_init() does not register an idle driver any more.

Accordingly, the cpuidle driver check in __acpi_processor_start() needs to be updated to avoid calling acpi_processor_power_init() without a cpuidle driver, in which case the registration of the cpuidle device in that function would lead to a NULL pointer dereference in __cpuidle_register_device().

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-43122"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-476"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-05-06T12:16:29Z",
    "severity": "MODERATE"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nACPI: processor: Update cpuidle driver check in __acpi_processor_start()\n\nCommit 7a8c994cbb2d (\"ACPI: processor: idle: Optimize ACPI idle\ndriver registration\") moved the ACPI idle driver registration to\nacpi_processor_driver_init() and acpi_processor_power_init() does\nnot register an idle driver any more.\n\nAccordingly, the cpuidle driver check in __acpi_processor_start() needs\nto be updated to avoid calling acpi_processor_power_init() without a\ncpuidle driver, in which case the registration of the cpuidle device\nin that function would lead to a NULL pointer dereference in\n__cpuidle_register_device().",
  "id": "GHSA-xrc9-fq2p-6mm2",
  "modified": "2026-05-12T21:31:26Z",
  "published": "2026-05-06T12:30:29Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-43122"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/0089ce1c056aee547115bdc25c223f8f88c08498"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/68f38f648e4b5bed2aeadd2f711e25302e6490f8"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/6cfed39c2ce64ac024bbde458a9727105e0b8c66"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…
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.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…