CVE-2022-50210 json
MIPS: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK
published 2025-06-18 16 mo ago modified 2026-06-17 4 mo ago also EUVD-2022-55472
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 14%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
MIPS: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK
When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS is selected, cpu_max_bits_warn() generates a runtime warning similar as below while we show /proc/cpuinfo. Fix this by using nr_cpu_ids (the runtime limit) instead of NR_CPUS to iterate CPUs.
[ 3.052463] ------------[ cut here ]------------ [ 3.059679] WARNING: CPU: 3 PID: 1 at include/linux/cpumask.h:108 show_cpuinfo+0x5e8/0x5f0 [ 3.070072] Modules linked in: efivarfs autofs4 [ 3.076257] CPU: 0 PID: 1 Comm: systemd Not tainted 5.19-rc5+ #1052 [ 3.084034] Hardware name: Loongson Loongson-3A4000-7A1000-1w-V0.1-CRB/Loongson-LS3A4000-7A1000-1w-EVB-V1.21, BIOS Loongson-UDK2018-V2.0.04082-beta7 04/27 [ 3.099465] Stack : 9000000100157b08 9000000000f18530 9000000000cf846c 9000000100154000 [ 3.109127] 9000000100157a50 0000000000000000 9000000100157a58 9000000000ef7430 [ 3.118774] 90000001001578e8 0000000000000040 0000000000000020 ffffffffffffffff [ 3.128412] 0000000000aaaaaa 1ab25f00eec96a37 900000010021de80 900000000101c890 [ 3.138056] 0000000000000000 0000000000000000 0000000000000000 0000000000aaaaaa [ 3.147711] ffff8000339dc220 0000000000000001 0000000006ab4000 0000000000000000 [ 3.157364] 900000000101c998 0000000000000004 9000000000ef7430 0000000000000000 [ 3.167012] 0000000000000009 000000000000006c 0000000000000000 0000000000000000 [ 3.176641] 9000000000d3de08 9000000001639390 90000000002086d8 00007ffff0080286 [ 3.186260] 00000000000000b0 0000000000000004 0000000000000000 0000000000071c1c [ 3.195868] ... [ 3.199917] Call Trace: [ 3.203941] [<98000000002086d8>] show_stack+0x38/0x14c [ 3.210666] [<9800000000cf846c>] dump_stack_lvl+0x60/0x88 [ 3.217625] [<980000000023d268>] __warn+0xd0/0x100 [ 3.223958] [<9800000000cf3c90>] warn_slowpath_fmt+0x7c/0xcc [ 3.231150] [<9800000000210220>] show_cpuinfo+0x5e8/0x5f0 [ 3.238080] [<98000000004f578c>] seq_read_iter+0x354/0x4b4 [ 3.245098] [<98000000004c2e90>] new_sync_read+0x17c/0x1c4 [ 3.252114] [<98000000004c5174>] vfs_read+0x138/0x1d0 [ 3.258694] [<98000000004c55f8>] ksys_read+0x70/0x100 [ 3.265265] [<9800000000cfde9c>] do_syscall+0x7c/0x94 [ 3.271820] [<9800000000202fe4>] handle_syscall+0xc4/0x160 [ 3.281824] ---[ end trace 8b484262b4b8c24c ]---
Patch / fix
- Linux Linux 4.9.326, 4.14.291, 4.19.256, 5.4.211, 5.10.137, 5.15.61, 5.18.18, 5.19.2, 6.0
- linux Debian 14, Debian 13, Debian 12 6.0.2-1
debian advisories DEBIAN-CVE-2022-50210
- linux Ubuntu 18.04 LTS 4.15.0-197.208
- linux Ubuntu 20.04 LTS 5.4.0-132.148
- linux Ubuntu 22.04 LTS 5.15.0-53.59
- linux-aws Ubuntu 18.04 LTS 4.15.0-1143.155
- linux-aws Ubuntu 20.04 LTS 5.4.0-1089.97
- linux-aws Ubuntu 22.04 LTS 5.15.0-1023.27
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1093.102
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1022.29
ubuntu advisories UBUNTU-CVE-2022-50210
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/d3ac4e47510ec0753ebe1e418a334ad202784aa8 commit
- git.kernel.org/stable/c/98aaa511957667ba26d6dabe28dfa210a8f53a63 commit
- git.kernel.org/stable/c/4cb392956ae392aec4aa06e661a0bb9146b0bace commit
- git.kernel.org/stable/c/274e44e2123417e0924c90d4b4531913b5f3aa2e commit
- git.kernel.org/stable/c/807adf6ffa8c3beedcd63b20f5a59c7d061df7d2 commit
- git.kernel.org/stable/c/e41db8a9ce696a3382a4f098878fd4d14bccd201 commit
- git.kernel.org/stable/c/8916ec149c79cb21f5454fa7840ad96f99cf51cf commit
- git.kernel.org/stable/c/7d305823e02217b29d41fca67e3cef87fd7bd688 commit
- git.kernel.org/stable/c/e1a534f5d074db45ae5cbac41d8912b98e96a006 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-50210 updated
kernel: MIPS: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/d3ac4e47510ec0753ebe1e418a334ad202784aa8
patch
-
git.kernel.org
/stable/c/98aaa511957667ba26d6dabe28dfa210a8f53a63
patch
-
git.kernel.org
/stable/c/4cb392956ae392aec4aa06e661a0bb9146b0bace
patch
-
git.kernel.org
/stable/c/274e44e2123417e0924c90d4b4531913b5f3aa2e
patch
-
git.kernel.org
/stable/c/807adf6ffa8c3beedcd63b20f5a59c7d061df7d2
patch
-
git.kernel.org
/stable/c/e41db8a9ce696a3382a4f098878fd4d14bccd201
patch
-
git.kernel.org
/stable/c/8916ec149c79cb21f5454fa7840ad96f99cf51cf
patch
-
git.kernel.org
/stable/c/7d305823e02217b29d41fca67e3cef87fd7bd688
patch
-
git.kernel.org
/stable/c/e1a534f5d074db45ae5cbac41d8912b98e96a006
patch
Sources
- CVE List CVE-2022-50210
- NVD CVE-2022-50210
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.