[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025061814-CVE-2022-50130-b9e9@gregkh>
Date: Wed, 18 Jun 2025 13:03:15 +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-50130: staging: fbtft: core: set smem_len before fb_deferred_io_init call
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
staging: fbtft: core: set smem_len before fb_deferred_io_init call
The fbtft_framebuffer_alloc() calls fb_deferred_io_init() before
initializing info->fix.smem_len. It is set to zero by the
framebuffer_alloc() function. It will trigger a WARN_ON() at the
start of fb_deferred_io_init() and the function will not do anything.
The Linux kernel CVE team has assigned CVE-2022-50130 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.18.3 with commit 6a9ae2fe887042f76fd3d334349e64e8ab3c55a2 and fixed in 5.18.18 with commit 5185c319e8ea67657e0d3edd520a7276516c506a
Issue introduced in 5.19 with commit 856082f021a28221db2c32bd0531614a8382be67 and fixed in 5.19.2 with commit 6ae6abe240306f878557d6eadd950a2e2561f59f
Issue introduced in 5.19 with commit 856082f021a28221db2c32bd0531614a8382be67 and fixed in 6.0 with commit 81e878887ff82a7dd42f22951391069a5d520627
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-50130
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/staging/fbtft/fbtft-core.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/4178bfa3fc9de556dfe248a6eabe29280f0ffda5
https://git.kernel.org/stable/c/5185c319e8ea67657e0d3edd520a7276516c506a
https://git.kernel.org/stable/c/6ae6abe240306f878557d6eadd950a2e2561f59f
https://git.kernel.org/stable/c/81e878887ff82a7dd42f22951391069a5d520627
Powered by blists - more mailing lists