linux-cve-announce - CVE-2025-38630: fbdev: imxfb: Check fb_add

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025082232-CVE-2025-38630-e14a@gregkh>
Date: Fri, 22 Aug 2025 18:00:39 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38630: fbdev: imxfb: Check fb_add_videomode to prevent null-ptr-deref

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

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

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

fbdev: imxfb: Check fb_add_videomode to prevent null-ptr-deref

fb_add_videomode() can fail with -ENOMEM when its internal kmalloc() cannot
allocate a struct fb_modelist.  If that happens, the modelist stays empty but
the driver continues to register.  Add a check for its return value to prevent
poteintial null-ptr-deref, which is similar to the commit 17186f1f90d3 ("fbdev:
Fix do_register_framebuffer to prevent null-ptr-deref in fb_videomode_to_var").

The Linux kernel CVE team has assigned CVE-2025-38630 to this issue.


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

	Issue introduced in 3.11 with commit 1b6c79361ba5ce30b40f0f7d6fc2421dc5fcbe0c and fixed in 6.1.148 with commit ac16154cccda8be10ee3ae188f10a06f3890bc5d
	Issue introduced in 3.11 with commit 1b6c79361ba5ce30b40f0f7d6fc2421dc5fcbe0c and fixed in 6.6.102 with commit 4b5d36cc3014986e6fac12eaa8433fe56801d4ce
	Issue introduced in 3.11 with commit 1b6c79361ba5ce30b40f0f7d6fc2421dc5fcbe0c and fixed in 6.12.42 with commit 40f0a51f6c54d46a94b9f1180339ede7ca7ee190
	Issue introduced in 3.11 with commit 1b6c79361ba5ce30b40f0f7d6fc2421dc5fcbe0c and fixed in 6.15.10 with commit 49377bac9e3bec1635065a033c9679214fe7593e
	Issue introduced in 3.11 with commit 1b6c79361ba5ce30b40f0f7d6fc2421dc5fcbe0c and fixed in 6.16.1 with commit f060441c153495750804133555cf0a211a856892
	Issue introduced in 3.11 with commit 1b6c79361ba5ce30b40f0f7d6fc2421dc5fcbe0c and fixed in 6.17-rc1 with commit da11e6a30e0bb8e911288bdc443b3dc8f6a7cac7

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-2025-38630
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/imxfb.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/ac16154cccda8be10ee3ae188f10a06f3890bc5d
	https://git.kernel.org/stable/c/4b5d36cc3014986e6fac12eaa8433fe56801d4ce
	https://git.kernel.org/stable/c/40f0a51f6c54d46a94b9f1180339ede7ca7ee190
	https://git.kernel.org/stable/c/49377bac9e3bec1635065a033c9679214fe7593e
	https://git.kernel.org/stable/c/f060441c153495750804133555cf0a211a856892
	https://git.kernel.org/stable/c/da11e6a30e0bb8e911288bdc443b3dc8f6a7cac7