CVE-2022-50771 Details
Description
In the Linux kernel, the following vulnerability has been resolved: rcu: Fix __this_cpu_read() lockdep warning in rcu_force_quiescent_state() Running rcutorture with non-zero fqs_duration module parameter in a kernel built with CONFIG_PREEMPTION=y results in the following splat: BUG: using __this_cpu_read() in preemptible [00000000] code: rcu_torture_fqs/398 caller is __this_cpu_preempt_check+0x13/0x20 CPU: 3 PID: 398 Comm: rcu_torture_fqs Not tainted 6.0.0-rc1-yoctodev-standard+ Call Trace: <TASK> dump_stack_lvl+0x5b/0x86 dump_stack+0x10/0x16 check_preemption_disabled+0xe5/0xf0 __this_cpu_preempt_check+0x13/0x20 rcu_force_quiescent_state.part.0+0x1c/0x170 rcu_force_quiescent_state+0x1e/0x30 rcu_torture_fqs+0xca/0x160 ? rcu_torture_boost+0x430/0x430 kthread+0x192/0x1d0 ? kthread_complete_and_exit+0x30/0x30 ret_from_fork+0x22/0x30 </TASK> The problem is that rcu_force_quiescent_state() uses __this_cpu_read() in preemptible code instead of the proper raw_cpu_read(). This commit therefore changes __this_cpu_read() to raw_cpu_read().
A lockdep warning related to the RCU (Read-Copy-Update) mechanism has been addressed in the Linux kernel. The issue arose in a preemptible kernel when running the rcutorture tool with a non-zero fqs_duration parameter. This combination triggered a warning because the rcu_force_quiescent_state() function improperly used __this_cpu_read() in preemptible code, instead of the correct raw_cpu_read(). The vulnerability is present in Linux kernel versions 6.0.0-rc1-yoctodev-standard and prior.
Users can upgrade to the latest stable version of the Linux kernel, where this issue has been fixed. Instructions for downloading the latest version can be found on the official Linux kernel website.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Dec 24, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/3d92527a919edd1aa381bdd6c299dd75a8167396 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/5a52380b8193cf8be6c4a6b94b86ef64ed80c0dc | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/80a3e7ab477b3655615fc1627c88c248d4ad28d9 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/98a5b1265a36e9d843a51ddd6c9fa02da50d2c57 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/a74af9b937707b42c3fd041aae1ed4ce2f337307 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/ceb1c8c9b8aa9199da46a0f29d2d5f08d9b44c15 | kernel.org | Source CodeVendor |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 10, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Dec 24, 2025 | New CVE Received | kernel.org |
Volerion