From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-64039: drm/msm/snapshot: fix dumping of the unaligned regions
Date: Sun, 19 Jul 2026 17:38:21 +0200 [thread overview]
Message-ID: <2026071905-CVE-2026-64039-d68a@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/msm/snapshot: fix dumping of the unaligned regions
The snapshotting code internally aligns data segment to 16 bytes. This
works fine for DPU code (where most of the regions are aligned), but
fails for snapshotting of the DSI data (because DSI data region is
shifted by 4 bytes). Fix the code by removing length alignment and by
accurately printing last registers in the region. While reworking the
code also fix the 16x memory overallocation in
msm_disp_state_dump_regs().
Patchwork: https://patchwork.freedesktop.org/patch/725449/
The Linux kernel CVE team has assigned CVE-2026-64039 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.14 with commit 98659487b845c05b6bed85d881713545db674c7c and fixed in 5.15.209 with commit 8fb070cf95847b29ef6cb15ec2c0de2bf4704676
Issue introduced in 5.14 with commit 98659487b845c05b6bed85d881713545db674c7c and fixed in 6.1.175 with commit cecd34e046121d788a70b5c8b4f8a88916637953
Issue introduced in 5.14 with commit 98659487b845c05b6bed85d881713545db674c7c and fixed in 6.6.142 with commit 070e40acc59ef7bedba0314f59971ba87fcc8ab0
Issue introduced in 5.14 with commit 98659487b845c05b6bed85d881713545db674c7c and fixed in 6.12.92 with commit 1ef79be774706dddcfcace0331fa7ff32a73c73e
Issue introduced in 5.14 with commit 98659487b845c05b6bed85d881713545db674c7c and fixed in 6.18.34 with commit cdd1aaf0ee962f50810b9aef7928f2313989d55f
Issue introduced in 5.14 with commit 98659487b845c05b6bed85d881713545db674c7c and fixed in 7.0.11 with commit 0c90ececfad3fc5c4c43a75ece0e2d736ab3def1
Issue introduced in 5.14 with commit 98659487b845c05b6bed85d881713545db674c7c and fixed in 7.1 with commit 76824d2467feb1828b745d6add2541918d7be3da
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-64039
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/msm/disp/msm_disp_snapshot_util.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/8fb070cf95847b29ef6cb15ec2c0de2bf4704676
https://git.kernel.org/stable/c/cecd34e046121d788a70b5c8b4f8a88916637953
https://git.kernel.org/stable/c/070e40acc59ef7bedba0314f59971ba87fcc8ab0
https://git.kernel.org/stable/c/1ef79be774706dddcfcace0331fa7ff32a73c73e
https://git.kernel.org/stable/c/cdd1aaf0ee962f50810b9aef7928f2313989d55f
https://git.kernel.org/stable/c/0c90ececfad3fc5c4c43a75ece0e2d736ab3def1
https://git.kernel.org/stable/c/76824d2467feb1828b745d6add2541918d7be3da
reply other threads:[~2026-07-19 15:41 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=2026071905-CVE-2026-64039-d68a@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox