From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2022-50814: crypto: hisilicon/zip - fix mismatch in get/set sgl_sge_nr
Date: Tue, 30 Dec 2025 13:09:18 +0100 [thread overview]
Message-ID: <2025123014-CVE-2022-50814-486d@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
crypto: hisilicon/zip - fix mismatch in get/set sgl_sge_nr
KASAN reported this Bug:
[17619.659757] BUG: KASAN: global-out-of-bounds in param_get_int+0x34/0x60
[17619.673193] Read of size 4 at addr fffff01332d7ed00 by task read_all/1507958
...
[17619.698934] The buggy address belongs to the variable:
[17619.708371] sgl_sge_nr+0x0/0xffffffffffffa300 [hisi_zip]
There is a mismatch in hisi_zip when get/set the variable sgl_sge_nr.
The type of sgl_sge_nr is u16, and get/set sgl_sge_nr by
param_get/set_int.
Replacing param_get/set_int to param_get/set_ushort can fix this bug.
The Linux kernel CVE team has assigned CVE-2022-50814 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.5 with commit f081fda293ffba54216a7dab66faba7275475006 and fixed in 5.10.150 with commit d88b88514ef28515ccfa1f1787c2aedef75a79dd
Issue introduced in 5.5 with commit f081fda293ffba54216a7dab66faba7275475006 and fixed in 5.15.75 with commit 272093471305261c4e07a2fc97c2d1e53cd56819
Issue introduced in 5.5 with commit f081fda293ffba54216a7dab66faba7275475006 and fixed in 5.19.17 with commit f8a983d6e01b198320d310cb1326364d7d973b2a
Issue introduced in 5.5 with commit f081fda293ffba54216a7dab66faba7275475006 and fixed in 6.0.3 with commit 5eaebd19fbb0e26e73a34f55d3b1dc310df0eb15
Issue introduced in 5.5 with commit f081fda293ffba54216a7dab66faba7275475006 and fixed in 6.1 with commit d74f9340097a881869c4c22ca376654cc2516ecc
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-50814
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/crypto/hisilicon/zip/zip_crypto.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/d88b88514ef28515ccfa1f1787c2aedef75a79dd
https://git.kernel.org/stable/c/272093471305261c4e07a2fc97c2d1e53cd56819
https://git.kernel.org/stable/c/f8a983d6e01b198320d310cb1326364d7d973b2a
https://git.kernel.org/stable/c/5eaebd19fbb0e26e73a34f55d3b1dc310df0eb15
https://git.kernel.org/stable/c/d74f9340097a881869c4c22ca376654cc2516ecc
reply other threads:[~2025-12-30 12:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025123014-CVE-2022-50814-486d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.