linux-cve-announce - CVE-2026-23222: crypto: omap - Allocate OMAP_CRYPTO_FORCE

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: <2026021806-CVE-2026-23222-3958@gregkh>
Date: Wed, 18 Feb 2026 15:54:11 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2026-23222: crypto: omap - Allocate OMAP_CRYPTO_FORCE_COPY scatterlists correctly

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

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

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

crypto: omap - Allocate OMAP_CRYPTO_FORCE_COPY scatterlists correctly

The existing allocation of scatterlists in omap_crypto_copy_sg_lists()
was allocating an array of scatterlist pointers, not scatterlist objects,
resulting in a 4x too small allocation.

Use sizeof(*new_sg) to get the correct object size.

The Linux kernel CVE team has assigned CVE-2026-23222 to this issue.


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

	Fixed in 6.6.125 with commit 6edf8df4bd29f7bfd245b67b2c31d905f1cfc14b
	Fixed in 6.12.72 with commit c184341920ed78b6466360ed7b45b8922586c38f
	Fixed in 6.18.11 with commit 2ed27b5a1174351148c3adbfc0cd86d54072ba2e
	Fixed in 6.19.1 with commit d1836c628cb72734eb5f7dfd4c996a9c18bba3ad

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-2026-23222
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/omap-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/6edf8df4bd29f7bfd245b67b2c31d905f1cfc14b
	https://git.kernel.org/stable/c/c184341920ed78b6466360ed7b45b8922586c38f
	https://git.kernel.org/stable/c/2ed27b5a1174351148c3adbfc0cd86d54072ba2e
	https://git.kernel.org/stable/c/d1836c628cb72734eb5f7dfd4c996a9c18bba3ad
	https://git.kernel.org/stable/c/1562b1fb7e17c1b3addb15e125c718b2be7f5512