CVE-2025-38630 [Medium] | Security Vulnerability in Linux Kernel

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").

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-01-08	0.06%	0.02%	-0.04%
2	2025-12-22	0.02%	0.06%	+0.04%
3	2025-08-23	—	0.02%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-01-08

0.06%

0.02%

-0.04%

2025-12-22

0.02%

0.06%

+0.04%

2025-08-23

—

0.02%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

3.6

[email protected]

OS Trackers for CVE-2025-38630

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2025-38630 not yet assigned priority: Debian including 2 source packages (linux, linux-6.1), 6 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5, open 1.	https://security-tracker.debian.org/tracker/CVE-2025-38630
`redhat`	—	—	https://access.redhat.com/security/cve/CVE-2025-38630
`suse`	medium	CVE-2025-38630 severity moderate: SUSE including 478 source package names (2.1.3-6.73:kernel-default-base-6.4.0-34.1.21.11, 2.1.3-7.50:kernel-default-6.4.0-34.1, …), 1082 product×package rows across 211 product lines (Container suse/sl-micro/6.0/base-os-container, Container suse/sl-micro/6.0/kvm-os-container, … (211 product lines)): Fixed 627, Known Affected 231, Known Not Affected 203, First Fixed 21.	https://www.suse.com/security/cve/CVE-2025-38630/
`ubuntu`	medium	CVE-2025-38630 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1414 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): DNE 1017, ignored 165, released 165, needed 45, not-affected 18, needs-triage 2, pending 2.	https://ubuntu.com/security/CVE-2025-38630

Affected software / configurations for CVE-2025-38630

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 3.11, < 5.4.297	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.5, < 5.10.241	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.11, < 5.15.190	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 6.1.148	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.2, < 6.6.102	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.7, < 6.12.42	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.13, < 6.15.10	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.16, < 6.16.1	cpe:2.3:o:linux:linux_kernel::::::::
debian	debian_linux	11.0	cpe:2.3:o:debian:debian_linux:11.0:::::::*

References for CVE-2025-38630

URL	Tags
https://git.kernel.org/stable/c/40f0a51f6c54d46a94b9f1180339ede7ca7ee190	Patch
https://git.kernel.org/stable/c/49377bac9e3bec1635065a033c9679214fe7593e	Patch
https://git.kernel.org/stable/c/4b5d36cc3014986e6fac12eaa8433fe56801d4ce	Patch
https://git.kernel.org/stable/c/69373502c2b5d364842c702c941d1171e4f35a7c	Patch
https://git.kernel.org/stable/c/ac16154cccda8be10ee3ae188f10a06f3890bc5d	Patch
https://git.kernel.org/stable/c/cca8f5a3991916729b39d797d01499c335137319	Patch
https://git.kernel.org/stable/c/da11e6a30e0bb8e911288bdc443b3dc8f6a7cac7	Patch
https://git.kernel.org/stable/c/f00c29e6755ead56baf2a9c1d3c4c0bb40af3612	Patch
https://git.kernel.org/stable/c/f060441c153495750804133555cf0a211a856892	Patch
https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html	Third Party Advisory

URL

CVE-2025-38630 | fbdev: imxfb: Check fb_add_videomode to prevent null-ptr-deref

Exploit prediction scoring system (EPSS) score for CVE-2025-38630

Common vulnerability scoring system (CVSS) metrics for CVE-2025-38630

Weakness enumeration for CVE-2025-38630

OS Trackers for CVE-2025-38630

Affected software / configurations for CVE-2025-38630

References for CVE-2025-38630