Linux Kernel up to 6.1.1 rcu __this_cpu_read state issue

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.4$0-$5k0.00

Summaryinfo

A vulnerability has been found in Linux Kernel up to 5.4.228/5.10.162/5.15.85/6.0.15/6.1.1 and classified as critical. This impacts the function __this_cpu_read of the component rcu. Performing a manipulation results in state issue. This vulnerability is identified as CVE-2022-50771. There is not any exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as critical, was found in Linux Kernel up to 5.4.228/5.10.162/5.15.85/6.0.15/6.1.1. This affects the function __this_cpu_read of the component rcu. The manipulation with an unknown input leads to a state issue vulnerability. CWE is classifying the issue as CWE-371. The impact remains unknown. The summary by CVE is:

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().

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2022-50771 since 12/24/2025. The exploitability is told to be difficult. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/21/2026).

The vulnerability scanner Nessus provides a plugin with the ID 279887 (Linux Distros Unpatched Vulnerability : CVE-2022-50771), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.4.229, 5.10.163, 5.15.86, 6.0.16 or 6.1.2 eliminates this vulnerability. Applying the patch 3d92527a919edd1aa381bdd6c299dd75a8167396/5a52380b8193cf8be6c4a6b94b86ef64ed80c0dc/98a5b1265a36e9d843a51ddd6c9fa02da50d2c57/a74af9b937707b42c3fd041aae1ed4ce2f337307/80a3e7ab477b3655615fc1627c88c248d4ad28d9/ceb1c8c9b8aa9199da46a0f29d2d5f08d9b44c15 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (279887) and CERT Bund (WID-SEC-2025-2929). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • SUSE openSUSE
  • Open Source Linux Kernel

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.6
VulDB Meta Temp Score: 4.4

VulDB Base Score: 4.6
VulDB Temp Score: 4.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: State issue
CWE: CWE-371
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 279887
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2022-50771

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.4.229/5.10.163/5.15.86/6.0.16/6.1.2
Patch: 3d92527a919edd1aa381bdd6c299dd75a8167396/5a52380b8193cf8be6c4a6b94b86ef64ed80c0dc/98a5b1265a36e9d843a51ddd6c9fa02da50d2c57/a74af9b937707b42c3fd041aae1ed4ce2f337307/80a3e7ab477b3655615fc1627c88c248d4ad28d9/ceb1c8c9b8aa9199da46a0f29d2d5f08d9b44c15

Timelineinfo

12/24/2025 Advisory disclosed
12/24/2025 +0 days CVE reserved
12/24/2025 +0 days VulDB entry created
04/21/2026 +118 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2022-50771 (🔒)
GCVE (CVE): GCVE-0-2022-50771
GCVE (VulDB): GCVE-100-338061
CERT Bund: WID-SEC-2025-2929 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 12/24/2025 15:00
Updated: 04/21/2026 08:19
Changes: 12/24/2025 15:00 (59), 12/25/2025 13:35 (1), 12/27/2025 23:03 (2), 12/30/2025 01:32 (7), 04/21/2026 08:19 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to know what is going to be exploited?

We predict KEV entries!