CVE-2025-68220: net: ethernet: ti: netcp: Standardize knav_dma_open_channel to return NULL on error
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.21% (FIRST EPSS).
- Fixed version: Linux Linux 2572c358ee434ce4b994472cceeb4043cbff5bc5, 3afeb909c3e2e0eb19b1e20506196e5f2d9c2259, 8427218ecbd7f8559c37972e66cb0fa06e82353b; azl3 kernel 6.6.117.1-1 on Azure Linux 3.0 6.6.119.3-1.
Low priority for now. Upgrade to Linux Linux 2572c358ee434ce4b994472cceeb4043cbff5bc5, 3afeb909c3e2e0eb19b1e20506196e5f2d9c2259, 8427218ecbd7f8559c37972e66cb0fa06e82353b; azl3 kernel 6.6.117.1-1 on Azure Linux 3.0 6.6.119.3-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: net: ethernet: ti: netcp: Standardize knav_dma_open_channel to return NULL on error Make knav_dma_open_channel consistently return NULL on error instead of ERR_PTR. Currently the header include/linux/soc/ti/knav_dma.h returns NULL when the driver is disabled, but the driver implementation does not even return NULL or ERR_PTR on failure, causing inconsistency in the users. This results in a crash in netcp_free_navigator_resources as followed (trimmed): Unhandled fault: alignment exception (0x221) at 0xfffffff2 [fffffff2] *pgd=80000800207003, *pmd=82ffda003, *pte=00000000 Internal error: : 221 [#1] SMP ARM Modules linked in: CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.17.0-rc7 #1 NONE Hardware name: Keystone PC is at knav_dma_close_channel+0x30/0x19c LR is at netcp_free_navigator_resources+0x2c/0x28c [... TRIM...] Call trace: knav_dma_close_channel from netcp_free_navigator_resources+0x2c/0x28c netcp_free_navigator_resources from netcp_ndo_open+0x430/0x46c netcp_ndo_open from __dev_open+0x114/0x29c __dev_open from __dev_change_flags+0x190/0x208 __dev_change_flags from netif_change_flags+0x1c/0x58 netif_change_flags from dev_change_flags+0x38/0xa0 dev_change_flags from ip_auto_config+0x2c4/0x11f0 ip_auto_config from do_one_initcall+0x58/0x200 do_one_initcall from kernel_init_freeable+0x1cc/0x238 kernel_init_freeable from kernel_init+0x1c/0x12c kernel_init from ret_from_fork+0x14/0x38 [... TRIM...] Standardize the error handling by making the function return NULL on all error conditions. The API is used in just the netcp_core.c so the impact is limited. Note, this change, in effect reverts commit 5b6cb43b4d62 ("net: ethernet: ti: netcp_core: return error while dma channel open issue"), but provides a less error prone implementation.
- Published
- Dec 16, 2025
- Updated
- Oct 14, 2026
- EPSS
- 0.2% · 11th 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
- 3.18affected
- 88139ed030583557751e279968e13e892ae10825 and later · before af6b10a13fc0aee37df4a8292414cc055c263fa3affected · git
- 88139ed030583557751e279968e13e892ae10825 and later · before 8427218ecbd7f8559c37972e66cb0fa06e82353baffected · git
- 88139ed030583557751e279968e13e892ae10825 and later · before 3afeb909c3e2e0eb19b1e20506196e5f2d9c2259affected · git
- 88139ed030583557751e279968e13e892ae10825 and later · before 2572c358ee434ce4b994472cceeb4043cbff5bc5affected · git
- 88139ed030583557751e279968e13e892ae10825 and later · before 952637c5b9be64539cd0e13ef88db71a1df46373affected · git
- 88139ed030583557751e279968e13e892ae10825 and later · before fbb53727ca789a8d27052aab4b77ca9e2a0fae2baffected · git
- 88139ed030583557751e279968e13e892ae10825 and later · before f9608637ecc165d7d6341df105aee44691461fb9affected · git
- 88139ed030583557751e279968e13e892ae10825 and later · before 90a88306eb874fe4bbdd860e6c9787f5bbc588b5affected · git
- before 3.18not 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.10-1 | 6.17.10-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-68218Dec 16, 2025 · nvme-multipath: fix lockdep WARN due to partition scan work30Monitor
- ← EarlierCVE-2025-68219Dec 16, 2025 · cifs: fix memory leak in smb3_fs_context_parse_param error path0Monitor
- Later →CVE-2025-68221Dec 16, 2025 · mptcp: fix address removal logic in mptcp_pm_nl_rm_addr0Monitor
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 | 2572c358ee434ce4b994472cceeb4043cbff5bc5 | Vendor (CNA) |
| Linux Linux | 3afeb909c3e2e0eb19b1e20506196e5f2d9c2259 | Vendor (CNA) |
| Linux Linux | 8427218ecbd7f8559c37972e66cb0fa06e82353b | Vendor (CNA) |
| Linux Linux | 90a88306eb874fe4bbdd860e6c9787f5bbc588b5 | Vendor (CNA) |
| Linux Linux | 952637c5b9be64539cd0e13ef88db71a1df46373 | Vendor (CNA) |
| Linux Linux | af6b10a13fc0aee37df4a8292414cc055c263fa3 | Vendor (CNA) |
| Linux Linux | f9608637ecc165d7d6341df105aee44691461fb9 | Vendor (CNA) |
| Linux Linux | fbb53727ca789a8d27052aab4b77ca9e2a0fae2b | Vendor (CNA) |
| azl3 kernel 6.6.117.1-1 on Azure Linux 3.0 | 6.6.119.3-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| 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 (7 more)Show less
- git.kernel.org/stable/c/3afeb909c3e2e0eb19b1e20506196e5f2d9c2259
- git.kernel.org/stable/c/8427218ecbd7f8559c37972e66cb0fa06e82353b
- git.kernel.org/stable/c/90a88306eb874fe4bbdd860e6c9787f5bbc588b5
- git.kernel.org/stable/c/952637c5b9be64539cd0e13ef88db71a1df46373
- git.kernel.org/stable/c/af6b10a13fc0aee37df4a8292414cc055c263fa3
- git.kernel.org/stable/c/f9608637ecc165d7d6341df105aee44691461fb9
- git.kernel.org/stable/c/fbb53727ca789a8d27052aab4b77ca9e2a0fae2b
Vendor advisories and official records. Exploit/PoC links are deliberately left out.