Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2022-50771rcu: Fix __this_cpu_read() lockdep warning in rcu_force_quiescent_state()

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

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.24% · top 84% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected d860d40327dde251d508a234fa00bd0d90fbb656 – < 3d92527a919edd1aa381bdd6c299dd75a8167396
    • affected d860d40327dde251d508a234fa00bd0d90fbb656 – < 5a52380b8193cf8be6c4a6b94b86ef64ed80c0dc
    • affected d860d40327dde251d508a234fa00bd0d90fbb656 – < 98a5b1265a36e9d843a51ddd6c9fa02da50d2c57
    • affected d860d40327dde251d508a234fa00bd0d90fbb656 – < a74af9b937707b42c3fd041aae1ed4ce2f337307
    • affected d860d40327dde251d508a234fa00bd0d90fbb656 – < 80a3e7ab477b3655615fc1627c88c248d4ad28d9
    • affected d860d40327dde251d508a234fa00bd0d90fbb656 – < ceb1c8c9b8aa9199da46a0f29d2d5f08d9b44c15
  • Linux · Linux

    • affected 3.17
    • unaffected < 3.17
    • unaffected 5.4.229 – ≤ 5.4.*
    • unaffected 5.10.163 – ≤ 5.10.*
    • unaffected 5.15.86 – ≤ 5.15.*
    • unaffected 6.0.16 – ≤ 6.0.*
    • unaffected 6.1.2 – ≤ 6.1.*
    • unaffected 6.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-50771 badge
[![CVE-2022-50771](https://cveledger.app/badge/CVE-2022-50771.svg)](https://cveledger.app/cve/CVE-2022-50771)

Record last updated .