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

In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Fix crash when rebind ccp device for ccp.ko When CONFIG_CRYPTO_DEV_CCP_DEBUGFS is enabled, rebinding the ccp device causes the following crash: $ echo '0000:0a:00.2' > /sys/bus/pci/drivers/ccp/unbind $ echo '0000:0a:00.2' > /sys/bus/pci/drivers/ccp/bind [ 204.976930] BUG: kernel NULL pointer dereference, address: 0000000000000098 [ 204.978026] #PF: supervisor write access in kernel mode [ 204.979126] #PF: error_code(0x0002) - not-present page [ 204.980226] PGD 0 P4D 0 [ 204.981317] Oops: Oops: 0002 [#1] SMP NOPTI ... [ 204.997852] Call Trace: [ 204.999074] <TASK> [ 205.000297] start_creating+0x9f/0x1c0 [ 205.001533] debugfs_create_dir+0x1f/0x170 [ 205.002769] ? srso_return_thunk+0x5/0x5f [ 205.004000] ccp5_debugfs_setup+0x87/0x170 [ccp] [ 205.005241] ccp5_init+0x8b2/0x960 [ccp] [ 205.006469] ccp_dev_init+0xd4/0x150 [ccp] [ 205.007709] sp_init+0x5f/0x80 [ccp] [ 205.008942] sp_pci_probe+0x283/0x2e0 [ccp] [ 205.010165] ? srso_return_thunk+0x5/0x5f [ 205.011376] local_pci_probe+0x4f/0xb0 [ 205.012584] pci_device_probe+0xdb/0x230 [ 205.013810] really_probe+0xed/0x380 [ 205.015024] __driver_probe_device+0x7e/0x160 [ 205.016240] device_driver_attach+0x2f/0x60 [ 205.017457] bind_store+0x7c/0xb0 [ 205.018663] drv_attr_store+0x28/0x40 [ 205.019868] sysfs_kf_write+0x5f/0x70 [ 205.021065] kernfs_fop_write_iter+0x145/0x1d0 [ 205.022267] vfs_write+0x308/0x440 [ 205.023453] ksys_write+0x6d/0xe0 [ 205.024616] __x64_sys_write+0x1e/0x30 [ 205.025778] x64_sys_call+0x16ba/0x2150 [ 205.026942] do_syscall_64+0x56/0x1e0 [ 205.028108] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 205.029276] RIP: 0033:0x7fbc36f10104 [ 205.030420] Code: 89 02 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 8d 05 e1 08 2e 00 8b 00 85 c0 75 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 f3 c3 66 90 41 54 55 49 89 d4 53 48 89 f5 This patch sets ccp_debugfs_dir to NULL after destroying it in ccp5_debugfs_destroy, allowing the directory dentry to be recreated when rebinding the ccp device. Tested on AMD Ryzen 7 1700X.

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

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-01-10

0.06%

0.02%

-0.04%

2025-12-19

0.02%

0.06%

+0.04%

2025-08-20

—

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

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2025-38581 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 6.	https://security-tracker.debian.org/tracker/CVE-2025-38581
`redhat`	low	—	https://access.redhat.com/security/cve/CVE-2025-38581
`suse`	medium	CVE-2025-38581 severity moderate: SUSE including 477 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, …), 975 product×package rows across 189 product lines (Container suse/sl-micro/6.0/base-os-container, Container suse/sl-micro/6.0/kvm-os-container, … (189 product lines)): Fixed 627, Known Affected 231, Known Not Affected 96, First Fixed 21.	https://www.suse.com/security/cve/CVE-2025-38581/
`ubuntu`	medium	CVE-2025-38581 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, released 165, ignored 162, needed 41, not-affected 25, needs-triage 2, pending 2.	https://ubuntu.com/security/CVE-2025-38581

Affected software / configurations for CVE-2025-38581

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

URL	Tags
https://git.kernel.org/stable/c/181698af38d3f93381229ad89c09b5bd0496661a	Patch
https://git.kernel.org/stable/c/20c0ed8dd65834e6bab464f54cd6ff68659bacb9	Patch
https://git.kernel.org/stable/c/2d4060f05e74dbee884ba723f6afd9282befc3c5	Patch
https://git.kernel.org/stable/c/64ec9a7e7a6398b172ab6feba60e952163a1c3d5	Patch
https://git.kernel.org/stable/c/6eadf50c1d894cb34f3237064063207460946040	Patch
https://git.kernel.org/stable/c/9dea08eac4f6d6fbbae59992978252e2edab995d	Patch
https://git.kernel.org/stable/c/a25ab6dfa0ce323ec308966988be6b675eb9d3e5	Patch
https://git.kernel.org/stable/c/ce63a83925964ab7564bd216bd92b80bc365492e	Patch
https://git.kernel.org/stable/c/db111468531777cac8b4beb6515a88a54b0c4a74	Patch
https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html	Mailing List Third Party Advisory
https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html	Mailing List Third Party Advisory

URL

CVE-2025-38581 | crypto: ccp - Fix crash when rebind ccp device for ccp.ko

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

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

Weakness enumeration for CVE-2025-38581

OS Trackers for CVE-2025-38581

Affected software / configurations for CVE-2025-38581

References for CVE-2025-38581