From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72245: gpu: host1x: Fix device reference leak in host1x_device_parse_dt() error path
Date: Sat, 15 Aug 2026 15:05:24 +0900 [thread overview]
Message-ID: <2026081552-CVE-2026-72245-724a@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
gpu: host1x: Fix device reference leak in host1x_device_parse_dt() error path
After device_initialize(), the embedded struct device in struct
host1x_device should be released through the device core with
put_device().
In host1x_device_add(), if host1x_device_parse_dt() fails, the current
error path frees the object directly with kfree(device). That bypasses
the normal device lifetime handling and leaks the reference held on the
embedded struct device.
The issue was identified by a static analysis tool I developed and
confirmed by manual review.
Fix this by using put_device() in the host1x_device_parse_dt() failure
path.
The Linux kernel CVE team has assigned CVE-2026-72245 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.0 with commit f4c5cf88fbd50e4779042268947b2e2f90c20484 and fixed in 5.10.261 with commit a408d89e20d38d78f540e1951dc4c6056ad662e1
Issue introduced in 4.0 with commit f4c5cf88fbd50e4779042268947b2e2f90c20484 and fixed in 5.15.212 with commit 4ee41361c637eafa80f5d88b46d0016e6cdb24db
Issue introduced in 4.0 with commit f4c5cf88fbd50e4779042268947b2e2f90c20484 and fixed in 6.1.178 with commit 3642d0a45214e3b4cf61bf5e75b04b490d0b3519
Issue introduced in 4.0 with commit f4c5cf88fbd50e4779042268947b2e2f90c20484 and fixed in 6.6.145 with commit edc7267b59a465c6ae7c5ffac2171c30962bd325
Issue introduced in 4.0 with commit f4c5cf88fbd50e4779042268947b2e2f90c20484 and fixed in 6.12.97 with commit 4454caa204a2edb19c62754ddb96e5dbca0d2f49
Issue introduced in 4.0 with commit f4c5cf88fbd50e4779042268947b2e2f90c20484 and fixed in 6.18.40 with commit c4d6442ac3ed00041fe4e1df715717ed78a7d37f
Issue introduced in 4.0 with commit f4c5cf88fbd50e4779042268947b2e2f90c20484 and fixed in 7.1.5 with commit 8559b1501f77a5b5d003790bec170ca449e0c674
Issue introduced in 4.0 with commit f4c5cf88fbd50e4779042268947b2e2f90c20484 and fixed in 7.2-rc1 with commit e75717f9aec04355777be41070890c6a815c76df
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-72245
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/host1x/bus.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/a408d89e20d38d78f540e1951dc4c6056ad662e1
https://git.kernel.org/stable/c/4ee41361c637eafa80f5d88b46d0016e6cdb24db
https://git.kernel.org/stable/c/3642d0a45214e3b4cf61bf5e75b04b490d0b3519
https://git.kernel.org/stable/c/edc7267b59a465c6ae7c5ffac2171c30962bd325
https://git.kernel.org/stable/c/4454caa204a2edb19c62754ddb96e5dbca0d2f49
https://git.kernel.org/stable/c/c4d6442ac3ed00041fe4e1df715717ed78a7d37f
https://git.kernel.org/stable/c/8559b1501f77a5b5d003790bec170ca449e0c674
https://git.kernel.org/stable/c/e75717f9aec04355777be41070890c6a815c76df
reply other threads:[~2026-08-15 6:18 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=2026081552-CVE-2026-72245-724a@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.