From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72264: fbdev: tridentfb: fix potential memory leak in trident_pci_probe()
Date: Sat, 15 Aug 2026 15:05:43 +0900 [thread overview]
Message-ID: <2026081555-CVE-2026-72264-a2df@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
fbdev: tridentfb: fix potential memory leak in trident_pci_probe()
In trident_pci_probe(), the memory allocated for modelist using
fb_videomode_to_modelist() is not freed in subsequent error paths.
Fix that by calling fb_destroy_modelist().
The Linux kernel CVE team has assigned CVE-2026-72264 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.4 with commit 6a5e3bd0c8bc1025bb5092f54d5aea38216c665e and fixed in 5.10.261 with commit 868432039a3fd7c2c0d515e48f33d5e43391666c
Issue introduced in 4.4 with commit 6a5e3bd0c8bc1025bb5092f54d5aea38216c665e and fixed in 5.15.212 with commit 089d149ccd7c3ac3d5e14ac65e558dcd9ec27583
Issue introduced in 4.4 with commit 6a5e3bd0c8bc1025bb5092f54d5aea38216c665e and fixed in 6.1.178 with commit de9cf16e39c0378716e9764fc0fbb6d4b45a1ee1
Issue introduced in 4.4 with commit 6a5e3bd0c8bc1025bb5092f54d5aea38216c665e and fixed in 6.6.145 with commit 8d16e5bc78478176621cac0f4c381136d3c92c5f
Issue introduced in 4.4 with commit 6a5e3bd0c8bc1025bb5092f54d5aea38216c665e and fixed in 6.12.97 with commit 5bdb6f11ad0398b11a3ae4d9104035f9dc628cdc
Issue introduced in 4.4 with commit 6a5e3bd0c8bc1025bb5092f54d5aea38216c665e and fixed in 6.18.40 with commit 4ebe2c3a7db6332aab3655f8c552ca387c1dc199
Issue introduced in 4.4 with commit 6a5e3bd0c8bc1025bb5092f54d5aea38216c665e and fixed in 7.1.5 with commit 2efd9797331a559b93ab888f451838f87bd6dfa3
Issue introduced in 4.4 with commit 6a5e3bd0c8bc1025bb5092f54d5aea38216c665e and fixed in 7.2-rc1 with commit 7a35ec619d9af8ee128320975c1252b8ad65f1e8
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-72264
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/video/fbdev/tridentfb.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/868432039a3fd7c2c0d515e48f33d5e43391666c
https://git.kernel.org/stable/c/089d149ccd7c3ac3d5e14ac65e558dcd9ec27583
https://git.kernel.org/stable/c/de9cf16e39c0378716e9764fc0fbb6d4b45a1ee1
https://git.kernel.org/stable/c/8d16e5bc78478176621cac0f4c381136d3c92c5f
https://git.kernel.org/stable/c/5bdb6f11ad0398b11a3ae4d9104035f9dc628cdc
https://git.kernel.org/stable/c/4ebe2c3a7db6332aab3655f8c552ca387c1dc199
https://git.kernel.org/stable/c/2efd9797331a559b93ab888f451838f87bd6dfa3
https://git.kernel.org/stable/c/7a35ec619d9af8ee128320975c1252b8ad65f1e8
reply other threads:[~2026-08-15 6:19 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=2026081555-CVE-2026-72264-a2df@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.