From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43397: drm/bridge: samsung-dsim: Fix memory leak in error path
Date: Fri, 8 May 2026 16:22:06 +0200 [thread overview]
Message-ID: <2026050838-CVE-2026-43397-2864@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/bridge: samsung-dsim: Fix memory leak in error path
In samsung_dsim_host_attach(), drm_bridge_add() is called to add the
bridge. However, if samsung_dsim_register_te_irq() or
pdata->host_ops->attach() fails afterwards, the function returns
without removing the bridge, causing a memory leak.
Fix this by adding proper error handling with goto labels to ensure
drm_bridge_remove() is called in all error paths. Also ensure that
samsung_dsim_unregister_te_irq() is called if the attach operation
fails after the TE IRQ has been registered.
samsung_dsim_unregister_te_irq() function is moved without changes
to be before samsung_dsim_host_attach() to avoid forward declaration.
The Linux kernel CVE team has assigned CVE-2026-43397 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.4 with commit e7447128ca4a250374d6721ee98e3e3cf99551a6 and fixed in 6.6.130 with commit 98310fe3a2a79671b739a5344c1a11d74c503e25
Issue introduced in 6.4 with commit e7447128ca4a250374d6721ee98e3e3cf99551a6 and fixed in 6.12.78 with commit 0b07f7d2c5a4078c2f1c11bb36685084fe4e5c95
Issue introduced in 6.4 with commit e7447128ca4a250374d6721ee98e3e3cf99551a6 and fixed in 6.18.19 with commit e6d779654cda63d632bd8dfcdcabd125057e30a5
Issue introduced in 6.4 with commit e7447128ca4a250374d6721ee98e3e3cf99551a6 and fixed in 6.19.9 with commit a40b92fb4b26d4cb1b5e439e55a56db7e79a82d1
Issue introduced in 6.4 with commit e7447128ca4a250374d6721ee98e3e3cf99551a6 and fixed in 7.0 with commit 803ec1faf7c1823e6e3b1f2aaa81be18528c9436
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-43397
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/bridge/samsung-dsim.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/98310fe3a2a79671b739a5344c1a11d74c503e25
https://git.kernel.org/stable/c/0b07f7d2c5a4078c2f1c11bb36685084fe4e5c95
https://git.kernel.org/stable/c/e6d779654cda63d632bd8dfcdcabd125057e30a5
https://git.kernel.org/stable/c/a40b92fb4b26d4cb1b5e439e55a56db7e79a82d1
https://git.kernel.org/stable/c/803ec1faf7c1823e6e3b1f2aaa81be18528c9436
reply other threads:[~2026-05-08 14:23 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=2026050838-CVE-2026-43397-2864@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