From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49336: drm/etnaviv: check for reaped mapping in etnaviv_iommu_unmap_gem
Date: Wed, 26 Feb 2025 03:10:10 +0100 [thread overview]
Message-ID: <2025022640-CVE-2022-49336-bc56@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/etnaviv: check for reaped mapping in etnaviv_iommu_unmap_gem
When the mapping is already reaped the unmap must be a no-op, as we
would otherwise try to remove the mapping twice, corrupting the involved
data structures.
The Linux kernel CVE team has assigned CVE-2022-49336 to this issue.
Affected and fixed versions
===========================
Fixed in 5.4.198 with commit 19323b3671a85788569d15685c8f83a05ec48cbb
Fixed in 5.10.121 with commit 436cff507f2a41230baacc3e2ef1d3b2d2653f40
Fixed in 5.15.46 with commit 03bd455a79f69d97fee3e3b212ab754442f10e5c
Fixed in 5.17.14 with commit 461c0fdf9434188875da9f10cfc86065866bb797
Fixed in 5.18.3 with commit 64f4edec081cb7c97c5e928529d0e1b0dbbffb83
Fixed in 5.19 with commit e168c25526cd0368af098095c2ded4a008007e1b
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-49336
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/gpu/drm/etnaviv/etnaviv_mmu.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/19323b3671a85788569d15685c8f83a05ec48cbb
https://git.kernel.org/stable/c/436cff507f2a41230baacc3e2ef1d3b2d2653f40
https://git.kernel.org/stable/c/03bd455a79f69d97fee3e3b212ab754442f10e5c
https://git.kernel.org/stable/c/461c0fdf9434188875da9f10cfc86065866bb797
https://git.kernel.org/stable/c/64f4edec081cb7c97c5e928529d0e1b0dbbffb83
https://git.kernel.org/stable/c/e168c25526cd0368af098095c2ded4a008007e1b
reply other threads:[~2025-02-26 2:13 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=2025022640-CVE-2022-49336-bc56@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@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.