Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2024-49926 — kernel

🟡 CVSS 5.5 — Medium ✅ No Known Exploit NVD
5.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

rcu-tasks: Fix access non-existent percpu rtpcp variable in rcu_tasks_need_gpcb()

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

rcu-tasks: Fix access non-existent percpu rtpcp variable in rcu_tasks_need_gpcb()

For kernels built with CONFIG_FORCE_NR_CPUS=y, the nr_cpu_ids is

defined as NR_CPUS instead of the number of possible cpus, this

will cause the following system panic:

smpboot: Allowing 4 CPUs, 0 hotplug CPUs

...

setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:512 nr_node_ids:1

...

BUG: unable to handle page fault for address: ffffffff9911c8c8

Oops: 0000 [#1] PREEMPT SMP PTI

CPU: 0 PID: 15 Comm: rcu_tasks_trace Tainted: G W

6.6.21 #1 5dc7acf91a5e8e9ac9dcfc35bee0245691283ea6

RIP: 0010:rcu_tasks_need_gpcb+0x25d/0x2c0

RSP: 0018:ffffa371c00a3e60 EFLAGS: 00010082

CR2: ffffffff9911c8c8 CR3: 000000040fa20005 CR4: 00000000001706f0

Call Trace:

<TASK>

? __die+0x23/0x80

? page_fault_oops+0xa4/0x180

? exc_page_fault+0x152/0x180

? asm_exc_page_fault+0x26/0x40

? rcu_tasks_need_gpcb+0x25d/0x2c0

? __pfx_rcu_tasks_kthread+0x40/0x40

rcu_tasks_one_gp+0x69/0x180

rcu_tasks_kthread+0x94/0xc0

kthread+0xe8/0x140

? __pfx_kthread+0x40/0x40

ret_from_fork+0x34/0x80

? __pfx_kthread+0x40/0x40

ret_from_fork_asm+0x1b/0x80

</TASK>

Considering that there may be holes in the CPU numbers, use the

maximum possible cpu number, instead of nr_cpu_ids, for configuring

enqueue and dequeue limits.

[ neeraj.upadhyay: Fix htmldocs build error reported by Stephen Rothwell ]

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

  • Attack vector: Local — a local account, shell or session on the host is needed.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: None.
  • Integrity impact: None.
  • Availability impact: High — total loss, or loss the attacker controls.

Affected software

CVE-2024-49926 is recorded against 2 packages.

  • kernel (from 6.11.0 up to 6.11.3)
  • linux-kernel (from 6.11 up to 6.11.3)

Timeline and source

Published on 21 October 2024 and last revised on 12 August 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

Other advisories for this package

kernel has other advisories on record. If you are patching this one, these are worth checking on the same host:

Details

Severity Medium
CVSS Score 5.5
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2024-10-21
Updated 2026-08-20
Modified 2026-08-12

Affected Packages

Software From version Fixed in
kernel 6.11.0 6.11.3
linux-kernel 6.11 6.11.3

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in kernel

CVE-2024-49926 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2024
✓