From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72268: fbdev: tdfxfb: fix potential memory leak in tdfxfb_probe()
Date: Sat, 15 Aug 2026 15:05:47 +0900 [thread overview]
Message-ID: <2026081556-CVE-2026-72268-6e55@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
fbdev: tdfxfb: fix potential memory leak in tdfxfb_probe()
In tdfxfb_probe(), the memory allocated for modelist using
fb_videomode_to_modelist() when CONFIG_FB_3DFX_I2C is defined, is not
freed in the subsequent error paths.
Fix that by calling fb_destroy_modelist().
The Linux kernel CVE team has assigned CVE-2026-72268 to this issue.
Affected and fixed versions
===========================
Issue introduced in 2.6.30 with commit 215059d2421f95c30d1fca6ff31357fcae9f67dc and fixed in 5.10.261 with commit 237611edf15172e4dc7fa9b3b71c2445602d3459
Issue introduced in 2.6.30 with commit 215059d2421f95c30d1fca6ff31357fcae9f67dc and fixed in 5.15.212 with commit 2199d70efc5bea0e9b4462a4f9e4c3d3c21c5d34
Issue introduced in 2.6.30 with commit 215059d2421f95c30d1fca6ff31357fcae9f67dc and fixed in 6.1.178 with commit b039e0693df003c5baa1e89630344f92a78afb15
Issue introduced in 2.6.30 with commit 215059d2421f95c30d1fca6ff31357fcae9f67dc and fixed in 6.6.145 with commit dfbb1a695d8891774c80c0e2a9192afb66469eb7
Issue introduced in 2.6.30 with commit 215059d2421f95c30d1fca6ff31357fcae9f67dc and fixed in 6.12.97 with commit b7b26adc2718ca8f81ca75cd03aee94269d00e8a
Issue introduced in 2.6.30 with commit 215059d2421f95c30d1fca6ff31357fcae9f67dc and fixed in 6.18.40 with commit e1ca9b8559e0f5959228626bdeaae530a1ee0337
Issue introduced in 2.6.30 with commit 215059d2421f95c30d1fca6ff31357fcae9f67dc and fixed in 7.1.5 with commit 2fd16a94bea5e0c3e93791436cf8a800b175762a
Issue introduced in 2.6.30 with commit 215059d2421f95c30d1fca6ff31357fcae9f67dc and fixed in 7.2-rc1 with commit bb019d755366cc3e777a12d4bf457ff289837370
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-72268
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/tdfxfb.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/237611edf15172e4dc7fa9b3b71c2445602d3459
https://git.kernel.org/stable/c/2199d70efc5bea0e9b4462a4f9e4c3d3c21c5d34
https://git.kernel.org/stable/c/b039e0693df003c5baa1e89630344f92a78afb15
https://git.kernel.org/stable/c/dfbb1a695d8891774c80c0e2a9192afb66469eb7
https://git.kernel.org/stable/c/b7b26adc2718ca8f81ca75cd03aee94269d00e8a
https://git.kernel.org/stable/c/e1ca9b8559e0f5959228626bdeaae530a1ee0337
https://git.kernel.org/stable/c/2fd16a94bea5e0c3e93791436cf8a800b175762a
https://git.kernel.org/stable/c/bb019d755366cc3e777a12d4bf457ff289837370
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=2026081556-CVE-2026-72268-6e55@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.