CVE-2025-68176: PCI: cadence: Check for the existence of cdns_pcie::ops before using it
Noroxi assessment
Priority: Monitor (action score 0/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.20% (FIRST EPSS).
- Fixed version: Linux Linux 0d0bb756f002810d249caee51f3f1c309f3cdab5, 1810b2fd7375de88a74976dcd402b29088e479ed, 363448d069e29685ca37a118065121e486387af3.
Low priority for now. Upgrade to Linux Linux 0d0bb756f002810d249caee51f3f1c309f3cdab5, 1810b2fd7375de88a74976dcd402b29088e479ed, 363448d069e29685ca37a118065121e486387af3 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: PCI: cadence: Check for the existence of cdns_pcie::ops before using it cdns_pcie::ops might not be populated by all the Cadence glue drivers. This is going to be true for the upcoming Sophgo platform which doesn't set the ops. Hence, add a check to prevent NULL pointer dereference. [mani: reworded subject and description]
- Published
- Dec 16, 2025
- Updated
- Oct 14, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
—
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
- 5.9affected
- 40d957e6f9eb3a8a585007b8b730340c829afbdb and later · before d5dbe92ac8a4ca6226093241f95f9cb1b0d2e0e1affected · git
- 40d957e6f9eb3a8a585007b8b730340c829afbdb and later · before eb3d29ca0820fa3d7cccad47d2da56c9ab5469edaffected · git
- 40d957e6f9eb3a8a585007b8b730340c829afbdb and later · before 0d0bb756f002810d249caee51f3f1c309f3cdab5affected · git
- 40d957e6f9eb3a8a585007b8b730340c829afbdb and later · before 1810b2fd7375de88a74976dcd402b29088e479edaffected · git
- 40d957e6f9eb3a8a585007b8b730340c829afbdb and later · before 953eb3796ef06b8ea3bf6bdde14156255bc75866affected · git
- 40d957e6f9eb3a8a585007b8b730340c829afbdb and later · before 363448d069e29685ca37a118065121e486387af3affected · git
- 40d957e6f9eb3a8a585007b8b730340c829afbdb and later · before 49a6c160ad4812476f8ae1a8f4ed6d15adfa6c09affected · git
- before 5.9not affected · semver
- 5.10.247 and later · up to and including 5.10.*not affected · semver
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.159-1 | 6.1.159-1 |
| Debian:13 | linux | before 6.12.63-1 | 6.12.63-1 |
| Debian:14 | linux | before 6.17.8-1 | 6.17.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-68174Dec 16, 2025 · amd/amdkfd: enhance kfd process check in switch partition31Monitor
- ← EarlierCVE-2025-68175Dec 16, 2025 · media: nxp: imx8-isi: Fix streaming cleanup on release31Monitor
- Later →CVE-2025-68177Dec 16, 2025 · cpufreq/longhaul: handle NULL policy in longhaul_exit0Monitor
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 | 0d0bb756f002810d249caee51f3f1c309f3cdab5 | Vendor (CNA) |
| Linux Linux | 1810b2fd7375de88a74976dcd402b29088e479ed | Vendor (CNA) |
| Linux Linux | 363448d069e29685ca37a118065121e486387af3 | Vendor (CNA) |
| Linux Linux | 49a6c160ad4812476f8ae1a8f4ed6d15adfa6c09 | Vendor (CNA) |
| Linux Linux | 953eb3796ef06b8ea3bf6bdde14156255bc75866 | Vendor (CNA) |
| Linux Linux | d5dbe92ac8a4ca6226093241f95f9cb1b0d2e0e1 | Vendor (CNA) |
| Linux Linux | eb3d29ca0820fa3d7cccad47d2da56c9ab5469ed | Vendor (CNA) |
| debian:linux | 6.1.159-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
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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 (6 more)Show less
- git.kernel.org/stable/c/1810b2fd7375de88a74976dcd402b29088e479ed
- git.kernel.org/stable/c/363448d069e29685ca37a118065121e486387af3
- git.kernel.org/stable/c/49a6c160ad4812476f8ae1a8f4ed6d15adfa6c09
- git.kernel.org/stable/c/953eb3796ef06b8ea3bf6bdde14156255bc75866
- git.kernel.org/stable/c/d5dbe92ac8a4ca6226093241f95f9cb1b0d2e0e1
- git.kernel.org/stable/c/eb3d29ca0820fa3d7cccad47d2da56c9ab5469ed
Vendor advisories and official records. Exploit/PoC links are deliberately left out.