linux-cve-announce - CVE-2022-49614: nvme: use struct group for generic command dwords

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: <2025022614-CVE-2022-49614-b2a0@gregkh>
Date: Wed, 26 Feb 2025 03:22:57 +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-49614: nvme: use struct group for generic command dwords

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

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

nvme: use struct group for generic command dwords

This will allow the trace event to know the full size of the data
intended to be copied and silence read overflow checks.

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


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

	Fixed in 5.18.13 with commit 3d8b35387e01cab217dc4691a6f770cbb6ed852c
	Fixed in 5.19 with commit 5c629dc9609dc43492a7bc8060cc6120875bf096

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-49614
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/nvme/host/trace.h
	include/linux/nvme.h


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/3d8b35387e01cab217dc4691a6f770cbb6ed852c
	https://git.kernel.org/stable/c/5c629dc9609dc43492a7bc8060cc6120875bf096