From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43105: drm/vc4: Fix memory leak of BO array in hang state
Date: Wed, 6 May 2026 09:41:39 +0200 [thread overview]
Message-ID: <2026050622-CVE-2026-43105-e58f@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/vc4: Fix memory leak of BO array in hang state
The hang state's BO array is allocated separately with kzalloc() in
vc4_save_hang_state() but never freed in vc4_free_hang_state(). Add the
missing kfree() for the BO array before freeing the hang state struct.
The Linux kernel CVE team has assigned CVE-2026-43105 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.5 with commit 214613656b5179f0daab6e0a080814b5100d45f0 and fixed in 6.6.136 with commit a812008fe3a0aebb778d277b35717f64e23d0302
Issue introduced in 4.5 with commit 214613656b5179f0daab6e0a080814b5100d45f0 and fixed in 6.12.83 with commit 0d3c014a84396a147705f523a8fd6fc873e76502
Issue introduced in 4.5 with commit 214613656b5179f0daab6e0a080814b5100d45f0 and fixed in 6.18.24 with commit 421cea4f71f7cf65abaae878562ee4aa2b684628
Issue introduced in 4.5 with commit 214613656b5179f0daab6e0a080814b5100d45f0 and fixed in 6.19.14 with commit b8138567c4a80fd76a647849ebd4284996cf4b17
Issue introduced in 4.5 with commit 214613656b5179f0daab6e0a080814b5100d45f0 and fixed in 7.0 with commit f4dfd6847b3e5d24e336bca6057485116d17aea4
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-43105
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/vc4/vc4_gem.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/a812008fe3a0aebb778d277b35717f64e23d0302
https://git.kernel.org/stable/c/0d3c014a84396a147705f523a8fd6fc873e76502
https://git.kernel.org/stable/c/421cea4f71f7cf65abaae878562ee4aa2b684628
https://git.kernel.org/stable/c/b8138567c4a80fd76a647849ebd4284996cf4b17
https://git.kernel.org/stable/c/f4dfd6847b3e5d24e336bca6057485116d17aea4
reply other threads:[~2026-05-06 7:42 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=2026050622-CVE-2026-43105-e58f@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 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.