[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091558-CVE-2022-50301-c26c@gregkh>
Date: Mon, 15 Sep 2025 16:46:03 +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-50301: iommu/omap: Fix buffer overflow in debugfs
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
iommu/omap: Fix buffer overflow in debugfs
There are two issues here:
1) The "len" variable needs to be checked before the very first write.
Otherwise if omap2_iommu_dump_ctx() with "bytes" less than 32 it is a
buffer overflow.
2) The snprintf() function returns the number of bytes that *would* have
been copied if there were enough space. But we want to know the
number of bytes which were *actually* copied so use scnprintf()
instead.
The Linux kernel CVE team has assigned CVE-2022-50301 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.19 with commit bd4396f09a4a9e77423e92ec9448217ab46f6edf and fixed in 4.9.331 with commit 706e359cf046c142db290244c3f4938b20fbe805
Issue introduced in 3.19 with commit bd4396f09a4a9e77423e92ec9448217ab46f6edf and fixed in 4.14.296 with commit ec53b99b6b9da8b501f001595a6260c03b42d5b7
Issue introduced in 3.19 with commit bd4396f09a4a9e77423e92ec9448217ab46f6edf and fixed in 4.19.262 with commit 648472df221f2bbffb433b964bcb87baccc586d8
Issue introduced in 3.19 with commit bd4396f09a4a9e77423e92ec9448217ab46f6edf and fixed in 5.4.220 with commit 4010a1afaae1c0fb9c2cac5de703bed29b1f1782
Issue introduced in 3.19 with commit bd4396f09a4a9e77423e92ec9448217ab46f6edf and fixed in 5.10.150 with commit 2fee0dbfaeaaa4bda04279ce772c4572b1429d04
Issue introduced in 3.19 with commit bd4396f09a4a9e77423e92ec9448217ab46f6edf and fixed in 5.15.75 with commit 0c7043a5b5c3b35f5dc8875757f71e7f491d64d4
Issue introduced in 3.19 with commit bd4396f09a4a9e77423e92ec9448217ab46f6edf and fixed in 5.19.17 with commit bd0438f534b2e31b12f0b39b355c5dc2bbdaf854
Issue introduced in 3.19 with commit bd4396f09a4a9e77423e92ec9448217ab46f6edf and fixed in 6.0.3 with commit 9814cc350e0765ce69244bf55ae4c8b29facd27e
Issue introduced in 3.19 with commit bd4396f09a4a9e77423e92ec9448217ab46f6edf and fixed in 6.1 with commit 184233a5202786b20220acd2d04ddf909ef18f29
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-50301
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/iommu/omap-iommu-debug.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/706e359cf046c142db290244c3f4938b20fbe805
https://git.kernel.org/stable/c/ec53b99b6b9da8b501f001595a6260c03b42d5b7
https://git.kernel.org/stable/c/648472df221f2bbffb433b964bcb87baccc586d8
https://git.kernel.org/stable/c/4010a1afaae1c0fb9c2cac5de703bed29b1f1782
https://git.kernel.org/stable/c/2fee0dbfaeaaa4bda04279ce772c4572b1429d04
https://git.kernel.org/stable/c/0c7043a5b5c3b35f5dc8875757f71e7f491d64d4
https://git.kernel.org/stable/c/bd0438f534b2e31b12f0b39b355c5dc2bbdaf854
https://git.kernel.org/stable/c/9814cc350e0765ce69244bf55ae4c8b29facd27e
https://git.kernel.org/stable/c/184233a5202786b20220acd2d04ddf909ef18f29
Powered by blists - more mailing lists