CVE-2025-68332: comedi: c6xdigio: Fix invalid PNP driver unregistration
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.19% (FIRST EPSS).
- Fixed version: Linux Linux 407b25bb9284d69c27309e691ab1e02f9e1c46ac, 698149d797d0178162f394c55d4ed52aa0e0b7f6, 72262330f7b3ad2130e800cecf02adcce3c32c77.
Low priority for now. Upgrade to Linux Linux 407b25bb9284d69c27309e691ab1e02f9e1c46ac, 698149d797d0178162f394c55d4ed52aa0e0b7f6, 72262330f7b3ad2130e800cecf02adcce3c32c77 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: comedi: c6xdigio: Fix invalid PNP driver unregistration The Comedi low-level driver "c6xdigio" seems to be for a parallel port connected device. When the Comedi core calls the driver's Comedi "attach" handler `c6xdigio_attach()` to configure a Comedi to use this driver, it tries to enable the parallel port PNP resources by registering a PNP driver with `pnp_register_driver()`, but ignores the return value. (The `struct pnp_driver` it uses has only the `name` and `id_table` members filled in.) The driver's Comedi "detach" handler `c6xdigio_detach()` unconditionally unregisters the PNP driver with `pnp_unregister_driver()`. It is possible for `c6xdigio_attach()` to return an error before it calls `pnp_register_driver()` and it is possible for the call to `pnp_register_driver()` to return an error (that is ignored). In both cases, the driver should not be calling `pnp_unregister_driver()` as it does in `c6xdigio_detach()`. (Note that `c6xdigio_detach()` will be called by the Comedi core if `c6xdigio_attach()` returns an error, or if the Comedi core decides to detach the Comedi device from the driver for some other reason.) The unconditional call to `pnp_unregister_driver()` without a previous successful call to `pnp_register_driver()` will cause `driver_unregister()` to issue a warning "Unexpected driver unregister!". This was detected by Syzbot [1]. Also, the PNP driver registration and unregistration should be done at module init and exit time, respectively, not when attaching or detaching Comedi devices to the driver. (There might be more than one Comedi device being attached to the driver, although that is unlikely.) Change the driver to do the PNP driver registration at module init time, and the unregistration at module exit time. Since `c6xdigio_detach()` now only calls `comedi_legacy_detach()`, remove the function and change the Comedi driver "detach" handler to `comedi_legacy_detach`. ------------------------------------------- [1] Syzbot sample crash report: Unexpected driver unregister! WARNING: CPU: 0 PID: 5970 at drivers/base/driver.c:273 driver_unregister drivers/base/driver.c:273 [inline] WARNING: CPU: 0 PID: 5970 at drivers/base/driver.c:273 driver_unregister+0x90/0xb0 drivers/base/driver.c:270 Modules linked in: CPU: 0 UID: 0 PID: 5970 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025 RIP: 0010:driver_unregister drivers/base/driver.c:273 [inline] RIP: 0010:driver_unregister+0x90/0xb0 drivers/base/driver.c:270 Code: 48 89 ef e8 c2 e6 82 fc 48 89 df e8 3a 93 ff ff 5b 5d e9 c3 6d d9 fb e8 be 6d d9 fb 90 48 c7 c7 e0 f8 1f 8c e8 51 a2 97 fb 90 <0f> 0b 90 90 5b 5d e9 a5 6d d9 fb e8 e0 f4 41 fc eb 94 e8 d9 f4 41 RSP: 0018:ffffc9000373f9a0 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffffffff8ff24720 RCX: ffffffff817b6ee8 RDX: ffff88807c932480 RSI: ffffffff817b6ef5 RDI: 0000000000000001 RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000001 R12: ffffffff8ff24660 R13: dffffc0000000000 R14: 0000000000000000 R15: ffff88814cca0000 FS: 000055556dab1500(0000) GS:ffff8881249d9000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000055f77f285cd0 CR3: 000000007d871000 CR4: 00000000003526f0 Call Trace: <TASK> comedi_device_detach_locked+0x12f/0xa50 drivers/comedi/drivers.c:207 comedi_device_detach+0x67/0xb0 drivers/comedi/drivers.c:215 comedi_device_attach+0x43d/0x900 drivers/comedi/drivers.c:1011 do_devconfig_ioctl+0x1b1/0x710 drivers/comedi/comedi_fops.c:872 comedi_unlocked_ioctl+0x165d/0x2f00 drivers/comedi/comedi_fops.c:2178 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl fs/ioctl.c:583 [inline] __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_sys ---truncated---
- Published
- Dec 22, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 9th 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.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.
—
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
- 2.6.30affected
- 2c89e159cd2f386285e9522d6476dd7e801bee22 and later · before 407b25bb9284d69c27309e691ab1e02f9e1c46acaffected · git
- 2c89e159cd2f386285e9522d6476dd7e801bee22 and later · before f7fa1f4670c3c358a451546f0b80b9231952912daffected · git
- 2c89e159cd2f386285e9522d6476dd7e801bee22 and later · before e8110402b0c24d822b0b933d87d50870d59667efaffected · git
- 2c89e159cd2f386285e9522d6476dd7e801bee22 and later · before 72b3627b0d3b819de49b29c2c8cb1c64d54536b9affected · git
- 2c89e159cd2f386285e9522d6476dd7e801bee22 and later · before 9fd8c8ad35c8d2390ce5ca2eb523c044bebdc072affected · git
- 2c89e159cd2f386285e9522d6476dd7e801bee22 and later · before 698149d797d0178162f394c55d4ed52aa0e0b7f6affected · git
- 2c89e159cd2f386285e9522d6476dd7e801bee22 and later · before 888f7e2847bcb9df8257e656e1e837828942c53baffected · git
- 2c89e159cd2f386285e9522d6476dd7e801bee22 and later · before 72262330f7b3ad2130e800cecf02adcce3c32c77affected · git
- before 2.6.30not 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.162-1 | 6.1.162-1 |
| Debian:13 | linux | before 6.12.63-1 | 6.12.63-1 |
| Debian:14 | linux | before 6.17.12-1 | 6.17.12-1 |
| openSUSE:Tumbleweed | kernel-source | before 6.18.5-1.1 | 6.18.5-1.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-68330Dec 22, 2025 · iio: accel: bmc150: Fix irq assumption regression0Monitor
- ← EarlierCVE-2025-68331Dec 22, 2025 · usb: uas: fix urb unmapping issue when the uas device is remove during ongoing data transfer0Monitor
- Later →CVE-2025-68334Dec 22, 2025 · platform/x86/amd/pmc: Add support for Van Gogh SoC0Monitor
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 | 407b25bb9284d69c27309e691ab1e02f9e1c46ac | Vendor (CNA) |
| Linux Linux | 698149d797d0178162f394c55d4ed52aa0e0b7f6 | Vendor (CNA) |
| Linux Linux | 72262330f7b3ad2130e800cecf02adcce3c32c77 | Vendor (CNA) |
| Linux Linux | 72b3627b0d3b819de49b29c2c8cb1c64d54536b9 | Vendor (CNA) |
| Linux Linux | 888f7e2847bcb9df8257e656e1e837828942c53b | Vendor (CNA) |
| Linux Linux | 9fd8c8ad35c8d2390ce5ca2eb523c044bebdc072 | Vendor (CNA) |
| Linux Linux | e8110402b0c24d822b0b933d87d50870d59667ef | Vendor (CNA) |
| Linux Linux | f7fa1f4670c3c358a451546f0b80b9231952912d | Vendor (CNA) |
| debian:linux | 6.1.162-1 · Debian:12 | Package registry (OSV) |
| opensuse:kernel-source | 6.18.5-1.1 · openSUSE:Tumbleweed | 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/698149d797d0178162f394c55d4ed52aa0e0b7f6
- git.kernel.org/stable/c/72262330f7b3ad2130e800cecf02adcce3c32c77
- git.kernel.org/stable/c/72b3627b0d3b819de49b29c2c8cb1c64d54536b9
- git.kernel.org/stable/c/888f7e2847bcb9df8257e656e1e837828942c53b
- git.kernel.org/stable/c/9fd8c8ad35c8d2390ce5ca2eb523c044bebdc072
- git.kernel.org/stable/c/e8110402b0c24d822b0b933d87d50870d59667ef
- git.kernel.org/stable/c/f7fa1f4670c3c358a451546f0b80b9231952912d
Vendor advisories and official records. Exploit/PoC links are deliberately left out.