Skip to main content
VulnerabilityPublished Updated

CVE-2024-49926: Linux kernel · rcu-tasks: Fix access non-existent percpu rtpcp variable in rcu_tasks_need_gpcb()

Affects Linux kernelSource GCVE Database

0
Compare

Not known to be exploited.

Data as of 30 Oct 2026, 15:04 UTC

Severity
High

Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Oct 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

AI-suggested

A fix has been implemented in the Linux kernel to address this issue by correcting the CPU number usage in the rcu_tasks_need_gpcb() function. Users should update to a kernel version that includes this fix. Since this is a kernel-level issue, applying the official kernel patch or upgrading to a fixed kernel release is the recommended mitigation.

Description

A vulnerability in the Linux kernel's rcu-tasks subsystem caused a system panic due to accessing a non-existent per-CPU variable when kernels are built with CONFIG_FORCE_NR_CPUS=y. This issue arises because nr_cpu_ids is defined as NR_CPUS instead of the actual number of possible CPUs, leading to a page fault and kernel panic. The fix involves using the maximum possible CPU number rather than nr_cpu_ids for certain configurations to prevent this panic.

References

Community reviews

Loading reviews…