GHSA-F9M5-PX7H-RQ87

Vulnerability from github – Published: 2025-10-24 18:30 – Updated: 2025-10-24 18:30
VLAI
Details

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

cfi: Fix __cfi_slowpath_diag RCU usage with cpuidle

RCU_NONIDLE usage during __cfi_slowpath_diag can result in an invalid RCU state in the cpuidle code path:

WARNING: CPU: 1 PID: 0 at kernel/rcu/tree.c:613 rcu_eqs_enter+0xe4/0x138 ... Call trace: rcu_eqs_enter+0xe4/0x138 rcu_idle_enter+0xa8/0x100 cpuidle_enter_state+0x154/0x3a8 cpuidle_enter+0x3c/0x58 do_idle.llvm.6590768638138871020+0x1f4/0x2ec cpu_startup_entry+0x28/0x2c secondary_start_kernel+0x1b8/0x220 __secondary_switched+0x94/0x98

Instead, call rcu_irq_enter/exit to wake up RCU only when needed and disable interrupts for the entire CFI shadow/module check when we do.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2022-49709"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-02-26T07:01:46Z",
    "severity": "MODERATE"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ncfi: Fix __cfi_slowpath_diag RCU usage with cpuidle\n\nRCU_NONIDLE usage during __cfi_slowpath_diag can result in an invalid\nRCU state in the cpuidle code path:\n\n  WARNING: CPU: 1 PID: 0 at kernel/rcu/tree.c:613 rcu_eqs_enter+0xe4/0x138\n  ...\n  Call trace:\n    rcu_eqs_enter+0xe4/0x138\n    rcu_idle_enter+0xa8/0x100\n    cpuidle_enter_state+0x154/0x3a8\n    cpuidle_enter+0x3c/0x58\n    do_idle.llvm.6590768638138871020+0x1f4/0x2ec\n    cpu_startup_entry+0x28/0x2c\n    secondary_start_kernel+0x1b8/0x220\n    __secondary_switched+0x94/0x98\n\nInstead, call rcu_irq_enter/exit to wake up RCU only when needed and\ndisable interrupts for the entire CFI shadow/module check when we do.",
  "id": "GHSA-f9m5-px7h-rq87",
  "modified": "2025-10-24T18:30:57Z",
  "published": "2025-10-24T18:30:56Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-49709"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/57cd6d157eb479f0a8e820fd36b7240845c8a937"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/75f3a5fa2ad049c85ab5d5ee1ed9cfaa7e62c5ed"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/ca3897f2ac02ceae5e6fa794f83c36f9885b93da"
    }
  ],
  "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…

Loading…

Loading…

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.


Loading…