CVE-2026-72269

linux: In the Linux kernel, the following vulnerability has been resolved: fbdev: uvesafb: fix potential memory leak in uve...

CVE-2026-72269 is fixed in 11 products on 1 platform, first by DEBIAN-CVE-2026-72269, released August 15, 2026. It is not reported as exploited. Patch Radar priority: Routine.

Routine
CVSS
n/a
No vendor severity
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0022
12th percentile

In the Linux kernel, the following vulnerability has been resolved: fbdev: uvesafb: fix potential memory leak in uvesafb_probe() Due to an incorrect goto label, memory allocated for modedb and modelist in uvesafb_vbe_init() is not freed in some error paths. Fix this by updating the goto label.

Where it's fixed

ProductFixed inFixReleased
Linux
kernel-64kb · sles 15.7 6.4.0-150700.53.90.1 SUSE-SU-2026:5091-1 Nov 7, 2026
kernel-azure · sles 15.7 6.4.0-150700.53.90.1 SUSE-SU-2026:5091-1 Nov 7, 2026
kernel-default · sles 15.7 6.4.0-150700.53.90.1 SUSE-SU-2026:5091-1 Nov 7, 2026
kernel-default-base · sles 15.7 6.4.0-150700.53.90.1.150700.17.51.1 SUSE-SU-2026:5091-1 Nov 7, 2026
kernel-docs · sles 15.7 6.4.0-150700.53.90.1 SUSE-SU-2026:5091-1 Nov 7, 2026
kernel-livepatch-SLE15-SP7_Update_24 · sles 15.7 1-150700.15.3.1 SUSE-SU-2026:5091-1 Nov 7, 2026
kernel-obs-build · sles 15.7 6.4.0-150700.53.90.1 SUSE-SU-2026:5091-1 Nov 7, 2026
kernel-source · sles 15.7 6.4.0-150700.53.90.1 SUSE-SU-2026:5091-1 Nov 7, 2026
kernel-syms · sles 15.7 6.4.0-150700.53.90.1 SUSE-SU-2026:5091-1 Nov 7, 2026
kernel-zfcpdump · sles 15.7 6.4.0-150700.53.90.1 SUSE-SU-2026:5091-1 Nov 7, 2026
linux · Debian 12.15 (bookworm) 6.1.180-1 DEBIAN-CVE-2026-72269 Aug 15, 2026
linux · Debian 13.5 (trixie) 6.12.100-1 DEBIAN-CVE-2026-72269 Aug 15, 2026
linux · Debian 14 7.1.5-1 DEBIAN-CVE-2026-72269 Aug 15, 2026

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.