All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-68475: reset: sunxi: fix memory region leak on ioremap failure
Date: Sat, 15 Aug 2026 15:01:17 +0900	[thread overview]
Message-ID: <2026081505-CVE-2026-68475-eb17@gregkh> (raw)

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

reset: sunxi: fix memory region leak on ioremap failure

In sunxi_reset_init(), when ioremap() fails, the memory region obtained
via request_mem_region() is not released, leading to a resource leak.

Add an err_mem_region label to properly release the memory region before
freeing the data structure.

The Linux kernel CVE team has assigned CVE-2026-68475 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 3.14 with commit 8f1ae77f466660b6da2455cccecc07ae631fa66d and fixed in 5.10.261 with commit 23af4ea217800a20c405d72e82b11e24e27721f3
	Issue introduced in 3.14 with commit 8f1ae77f466660b6da2455cccecc07ae631fa66d and fixed in 5.15.212 with commit ec836995c00a1968e403ef6beb53a73a9b0f318c
	Issue introduced in 3.14 with commit 8f1ae77f466660b6da2455cccecc07ae631fa66d and fixed in 6.1.178 with commit b4d7333849839ff42e1bc802d5b5f63d71c65add
	Issue introduced in 3.14 with commit 8f1ae77f466660b6da2455cccecc07ae631fa66d and fixed in 6.6.145 with commit 6dc0c8cd9c8a84808c6df760024d2604bc6d31fe
	Issue introduced in 3.14 with commit 8f1ae77f466660b6da2455cccecc07ae631fa66d and fixed in 6.12.97 with commit 01e43f4e7d12dae6fa82ae1b2e91c9ce07e06cd8
	Issue introduced in 3.14 with commit 8f1ae77f466660b6da2455cccecc07ae631fa66d and fixed in 6.18.40 with commit 82753ac86cb3d641b8634a61335fd0f04a61cc1a
	Issue introduced in 3.14 with commit 8f1ae77f466660b6da2455cccecc07ae631fa66d and fixed in 7.1.5 with commit d826d3e04c5bd9d284ba29f330246a317a8a7023
	Issue introduced in 3.14 with commit 8f1ae77f466660b6da2455cccecc07ae631fa66d and fixed in 7.2-rc4 with commit 1a8c89f8c112c75e84ff9a140f969e372aed0c9a

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-68475
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/reset/reset-sunxi.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/23af4ea217800a20c405d72e82b11e24e27721f3
	https://git.kernel.org/stable/c/ec836995c00a1968e403ef6beb53a73a9b0f318c
	https://git.kernel.org/stable/c/b4d7333849839ff42e1bc802d5b5f63d71c65add
	https://git.kernel.org/stable/c/6dc0c8cd9c8a84808c6df760024d2604bc6d31fe
	https://git.kernel.org/stable/c/01e43f4e7d12dae6fa82ae1b2e91c9ce07e06cd8
	https://git.kernel.org/stable/c/82753ac86cb3d641b8634a61335fd0f04a61cc1a
	https://git.kernel.org/stable/c/d826d3e04c5bd9d284ba29f330246a317a8a7023
	https://git.kernel.org/stable/c/1a8c89f8c112c75e84ff9a140f969e372aed0c9a

                 reply	other threads:[~2026-08-15  6:06 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=2026081505-CVE-2026-68475-eb17@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.