linux-cve-announce - CVE-2022-50099: video: fbdev: arkfb: Check the size of screen before memset

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025061803-CVE-2022-50099-29c6@gregkh>
Date: Wed, 18 Jun 2025 13:02:44 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50099: video: fbdev: arkfb: Check the size of screen before memset_io()

From: Greg Kroah-Hartman <gregkh@...nel.org>

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

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

video: fbdev: arkfb: Check the size of screen before memset_io()

In the function arkfb_set_par(), the value of 'screen_size' is
calculated by the user input. If the user provides the improper value,
the value of 'screen_size' may larger than 'info->screen_size', which
may cause the following bug:

[  659.399066] BUG: unable to handle page fault for address: ffffc90003000000
[  659.399077] #PF: supervisor write access in kernel mode
[  659.399079] #PF: error_code(0x0002) - not-present page
[  659.399094] RIP: 0010:memset_orig+0x33/0xb0
[  659.399116] Call Trace:
[  659.399122]  arkfb_set_par+0x143f/0x24c0
[  659.399130]  fb_set_var+0x604/0xeb0
[  659.399161]  do_fb_ioctl+0x234/0x670
[  659.399189]  fb_ioctl+0xdd/0x130

Fix the this by checking the value of 'screen_size' before memset_io().

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


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

	Issue introduced in 2.6.22 with commit 681e14730c73cc2c71af282c001de6bc71c22f00 and fixed in 4.14.291 with commit 4a20c5510aa2c031a096a58deb356e91609781c9
	Issue introduced in 2.6.22 with commit 681e14730c73cc2c71af282c001de6bc71c22f00 and fixed in 4.19.256 with commit 352305ea50d682b8e081d826da53caf9e744d7d0
	Issue introduced in 2.6.22 with commit 681e14730c73cc2c71af282c001de6bc71c22f00 and fixed in 5.4.211 with commit 53198b81930e567ad6b879812d88052a1e8ac79e
	Issue introduced in 2.6.22 with commit 681e14730c73cc2c71af282c001de6bc71c22f00 and fixed in 5.10.137 with commit 09e733d6ac948e6fda4b16252e44ea46f98fc8b4
	Issue introduced in 2.6.22 with commit 681e14730c73cc2c71af282c001de6bc71c22f00 and fixed in 5.15.61 with commit 0701df594bc1d7ae55fed407fb65dd90a93f8a9c
	Issue introduced in 2.6.22 with commit 681e14730c73cc2c71af282c001de6bc71c22f00 and fixed in 5.18.18 with commit 8bcb1a06e3091716b7cbebe0e91d1de9895068cd
	Issue introduced in 2.6.22 with commit 681e14730c73cc2c71af282c001de6bc71c22f00 and fixed in 5.19.2 with commit 2ce61c39c2a0b8ec82f48e0f7136f0dac105ae75
	Issue introduced in 2.6.22 with commit 681e14730c73cc2c71af282c001de6bc71c22f00 and fixed in 6.0 with commit 96b550971c65d54d64728d8ba973487878a06454

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-50099
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:
	drivers/video/fbdev/arkfb.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/4a20c5510aa2c031a096a58deb356e91609781c9
	https://git.kernel.org/stable/c/352305ea50d682b8e081d826da53caf9e744d7d0
	https://git.kernel.org/stable/c/53198b81930e567ad6b879812d88052a1e8ac79e
	https://git.kernel.org/stable/c/09e733d6ac948e6fda4b16252e44ea46f98fc8b4
	https://git.kernel.org/stable/c/0701df594bc1d7ae55fed407fb65dd90a93f8a9c
	https://git.kernel.org/stable/c/8bcb1a06e3091716b7cbebe0e91d1de9895068cd
	https://git.kernel.org/stable/c/2ce61c39c2a0b8ec82f48e0f7136f0dac105ae75
	https://git.kernel.org/stable/c/96b550971c65d54d64728d8ba973487878a06454