CVE-2025-38581: crypto: ccp - Fix crash when rebind ccp device for ccp.ko
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 181698af38d3f93381229ad89c09b5bd0496661a, 20c0ed8dd65834e6bab464f54cd6ff68659bacb9, 2d4060f05e74dbee884ba723f6afd9282befc3c5; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1.
Low priority for now. Upgrade to Linux Linux 181698af38d3f93381229ad89c09b5bd0496661a, 20c0ed8dd65834e6bab464f54cd6ff68659bacb9, 2d4060f05e74dbee884ba723f6afd9282befc3c5; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 19, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-476
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel5.5 and later · before 5.10.241
- linux linux kernel5.11 and later · before 5.15.190
- linux linux kernel5.16 and later · before 6.1.148
- linux linux kernel4.13 and later · before 5.4.297
- linux linux kernel6.7 and later · before 6.12.42
- linux linux kernel6.13 and later · before 6.15.10
- linux linux kernel6.16 and later · before 6.16.1
- linux linux kernel6.2 and later · before 6.6.102
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.13affected
- 3cdbe346ed3f380eae1cb3e9febfe703e7d8a7b0 and later · before a25ab6dfa0ce323ec308966988be6b675eb9d3e5affected · git
- 3cdbe346ed3f380eae1cb3e9febfe703e7d8a7b0 and later · before ce63a83925964ab7564bd216bd92b80bc365492eaffected · git
- 3cdbe346ed3f380eae1cb3e9febfe703e7d8a7b0 and later · before 20c0ed8dd65834e6bab464f54cd6ff68659bacb9affected · git
- 3cdbe346ed3f380eae1cb3e9febfe703e7d8a7b0 and later · before 2d4060f05e74dbee884ba723f6afd9282befc3c5affected · git
- 3cdbe346ed3f380eae1cb3e9febfe703e7d8a7b0 and later · before db111468531777cac8b4beb6515a88a54b0c4a74affected · git
- 3cdbe346ed3f380eae1cb3e9febfe703e7d8a7b0 and later · before 9dea08eac4f6d6fbbae59992978252e2edab995daffected · git
- 3cdbe346ed3f380eae1cb3e9febfe703e7d8a7b0 and later · before 6eadf50c1d894cb34f3237064063207460946040affected · git
- 3cdbe346ed3f380eae1cb3e9febfe703e7d8a7b0 and later · before 64ec9a7e7a6398b172ab6feba60e952163a1c3d5affected · git
- 3cdbe346ed3f380eae1cb3e9febfe703e7d8a7b0 and later · before 181698af38d3f93381229ad89c09b5bd0496661aaffected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.148-1 | 6.1.148-1 |
| Debian:13 | linux | before 6.12.43-1 | 6.12.43-1 |
| Debian:14 | linux | before 6.16.3-1 | 6.16.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-38579Aug 19, 2025 · f2fs: fix KMSAN uninit-value in extent_info usage31Monitor
- ← EarlierCVE-2025-38580Aug 19, 2025 · ext4: fix inode use after free in ext4_end_io_rsv_work()31Monitor
- Later →CVE-2025-38583Aug 19, 2025 · clk: xilinx: vcu: unregister pll_post only if registered correctly22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 181698af38d3f93381229ad89c09b5bd0496661a | Vendor (CNA) |
| Linux Linux | 20c0ed8dd65834e6bab464f54cd6ff68659bacb9 | Vendor (CNA) |
| Linux Linux | 2d4060f05e74dbee884ba723f6afd9282befc3c5 | Vendor (CNA) |
| Linux Linux | 64ec9a7e7a6398b172ab6feba60e952163a1c3d5 | Vendor (CNA) |
| Linux Linux | 6eadf50c1d894cb34f3237064063207460946040 | Vendor (CNA) |
| Linux Linux | 9dea08eac4f6d6fbbae59992978252e2edab995d | Vendor (CNA) |
| Linux Linux | a25ab6dfa0ce323ec308966988be6b675eb9d3e5 | Vendor (CNA) |
| Linux Linux | ce63a83925964ab7564bd216bd92b80bc365492e | Vendor (CNA) |
| Linux Linux | db111468531777cac8b4beb6515a88a54b0c4a74 | Vendor (CNA) |
| azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 | 6.6.104.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.148-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (10 more)Show less
- git.kernel.org/stable/c/20c0ed8dd65834e6bab464f54cd6ff68659bacb9
- git.kernel.org/stable/c/2d4060f05e74dbee884ba723f6afd9282befc3c5
- git.kernel.org/stable/c/64ec9a7e7a6398b172ab6feba60e952163a1c3d5
- git.kernel.org/stable/c/6eadf50c1d894cb34f3237064063207460946040
- git.kernel.org/stable/c/9dea08eac4f6d6fbbae59992978252e2edab995d
- git.kernel.org/stable/c/a25ab6dfa0ce323ec308966988be6b675eb9d3e5
- git.kernel.org/stable/c/ce63a83925964ab7564bd216bd92b80bc365492e
- git.kernel.org/stable/c/db111468531777cac8b4beb6515a88a54b0c4a74
- lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.