linux-cve-announce - CVE-2022-49034: sh: cpuinfo: Fix a warning for CONFIG_CPUMASK

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024122709-CVE-2022-49034-9cc5@gregkh>
Date: Fri, 27 Dec 2024 14:52:10 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2022-49034: sh: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK

Description
===========

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

sh: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK

When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS are selected,
cpu_max_bits_warn() generates a runtime warning similar as below when
showing /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.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] [<90000000002086d8>] show_stack+0x38/0x14c
[    3.210666] [<9000000000cf846c>] dump_stack_lvl+0x60/0x88
[    3.217625] [<900000000023d268>] __warn+0xd0/0x100
[    3.223958] [<9000000000cf3c90>] warn_slowpath_fmt+0x7c/0xcc
[    3.231150] [<9000000000210220>] show_cpuinfo+0x5e8/0x5f0
[    3.238080] [<90000000004f578c>] seq_read_iter+0x354/0x4b4
[    3.245098] [<90000000004c2e90>] new_sync_read+0x17c/0x1c4
[    3.252114] [<90000000004c5174>] vfs_read+0x138/0x1d0
[    3.258694] [<90000000004c55f8>] ksys_read+0x70/0x100
[    3.265265] [<9000000000cfde9c>] do_syscall+0x7c/0x94
[    3.271820] [<9000000000202fe4>] handle_syscall+0xc4/0x160
[    3.281824] ---[ end trace 8b484262b4b8c24c ]---

The Linux kernel CVE team has assigned CVE-2022-49034 to this issue.


Affected and fixed versions
===========================

	Fixed in 4.19.325 with commit 8fbb57eabfc8ae67115cb47f904614c99d626a89
	Fixed in 5.4.287 with commit f8f26cf69003a37ffa947631fc0e6fe6daee624a
	Fixed in 5.10.231 with commit 77755dc95ff2f9a3e473acc1e039f498629949ea
	Fixed in 5.15.174 with commit e2b91997db286a5dd3cca6d5d9c20004851f22eb
	Fixed in 6.1.120 with commit 2b6b8e011fab680a223b5e07a3c64774156ec6fe
	Fixed in 6.6.64 with commit 09faf32c682ea4a547200b8b9e04d8b3c8e84b55
	Fixed in 6.11.11 with commit 39373f6f89f52770a5405d30dddd08a27d097872
	Fixed in 6.12.2 with commit 701e32900683378d93693fec15d133e2c5f7ada2
	Fixed in 6.13-rc1 with commit 3c891f7c6a4e90bb1199497552f24b26e46383bc

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2022-49034
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	arch/sh/kernel/cpu/proc.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/8fbb57eabfc8ae67115cb47f904614c99d626a89
	https://git.kernel.org/stable/c/f8f26cf69003a37ffa947631fc0e6fe6daee624a
	https://git.kernel.org/stable/c/77755dc95ff2f9a3e473acc1e039f498629949ea
	https://git.kernel.org/stable/c/e2b91997db286a5dd3cca6d5d9c20004851f22eb
	https://git.kernel.org/stable/c/2b6b8e011fab680a223b5e07a3c64774156ec6fe
	https://git.kernel.org/stable/c/09faf32c682ea4a547200b8b9e04d8b3c8e84b55
	https://git.kernel.org/stable/c/39373f6f89f52770a5405d30dddd08a27d097872
	https://git.kernel.org/stable/c/701e32900683378d93693fec15d133e2c5f7ada2
	https://git.kernel.org/stable/c/3c891f7c6a4e90bb1199497552f24b26e46383bc