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

In the Linux kernel, the following vulnerability has been resolved: clk: imx95-blk-ctl: Fix synchronous abort When enabling runtime PM for clock suppliers that also belong to a power domain, the following crash is thrown: error: synchronous external abort: 0000000096000010 [#1] PREEMPT SMP Workqueue: events_unbound deferred_probe_work_func pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : clk_mux_get_parent+0x60/0x90 lr : clk_core_reparent_orphans_nolock+0x58/0xd8 Call trace: clk_mux_get_parent+0x60/0x90 clk_core_reparent_orphans_nolock+0x58/0xd8 of_clk_add_hw_provider.part.0+0x90/0x100 of_clk_add_hw_provider+0x1c/0x38 imx95_bc_probe+0x2e0/0x3f0 platform_probe+0x70/0xd8 Enabling runtime PM without explicitly resuming the device caused the power domain cut off after clk_register() is called. As a result, a crash happens when the clock hardware provider is added and attempts to access the BLK_CTL register. Fix this by using devm_pm_runtime_enable() instead of pm_runtime_enable() and getting rid of the pm_runtime_disable() in the cleanup path.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-08-23	—	0.02%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

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-38631

vendor	priority	summary	link
`debian`	unimportant	CVE-2025-38631 unimportant priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2025-38631
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2025-38631
`suse`	medium	CVE-2025-38631 severity moderate: SUSE including 94 source package names (cluster-md-kmp-64kb-6.12.0-160000.6.1, cluster-md-kmp-default, …), 481 product×package rows across 86 product lines (Image SLES-Azure-3P, Image SLES-Azure-Basic, … (86 product lines)): Known Not Affected 283, Fixed 177, First Fixed 21.	https://www.suse.com/security/cve/CVE-2025-38631/
`ubuntu`	medium	CVE-2025-38631 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 161, not-affected 129, released 103, needs-triage 2, needed 1, pending 1.	https://ubuntu.com/security/CVE-2025-38631

Affected software / configurations for CVE-2025-38631

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 6.10, < 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::::::::

References for CVE-2025-38631

URL	Tags
https://git.kernel.org/stable/c/533dc3cb375cabd8a2beba293d63ef2acd3d0005	Patch
https://git.kernel.org/stable/c/9f0ee0baf25b46bb82655c687718ebb0ae1def7b	Patch
https://git.kernel.org/stable/c/b08217a257215ed9130fce93d35feba66b49bf0a	Patch
https://git.kernel.org/stable/c/c1dead8bb303f86905ea6a09e5acda931165453b	Patch

URL

CVE-2025-38631 | clk: imx95-blk-ctl: Fix synchronous abort

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

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

Weakness enumeration for CVE-2025-38631

OS Trackers for CVE-2025-38631

Affected software / configurations for CVE-2025-38631

References for CVE-2025-38631