CVE-2025-68257comedi: check device's attached status in compat ioctls
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 89% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: comedi: check device's attached status in compat ioctls Syzbot identified an issue [1] that crashes kernel, seemingly due to unexistent callback dev->get_valid_routes(). By all means, this should not occur as said callback must always be set to get_zero_valid_routes() in __comedi_device_postconfig(). As the crash seems to appear exclusively in i386 kernels, at least, judging from [1] reports, the blame lies with compat versions of standard IOCTL handlers. Several of them are modified and do not use comedi_unlocked_ioctl(). While functionality of these ioctls essentially copy their original versions, they do not have required sanity check for device's attached status. This, in turn, leads to a possibility of calling select IOCTLs on a device that has not been properly setup, even via COMEDI_DEVCONFIG. Doing so on unconfigured devices means that several crucial steps are missed, for instance, specifying dev->get_valid_routes() callback. Fix this somewhat crudely by ensuring device's attached status before performing any ioctls, improving logic consistency between modern and compat functions. [1] Syzbot report: BUG: kernel NULL pointer dereference, address: 0000000000000000 ... CR2: ffffffffffffffd6 CR3: 000000006c717000 CR4: 0000000000352ef0 Call Trace: <TASK> get_valid_routes drivers/comedi/comedi_fops.c:1322 [inline] parse_insn+0x78c/0x1970 drivers/comedi/comedi_fops.c:1401 do_insnlist_ioctl+0x272/0x700 drivers/comedi/comedi_fops.c:1594 compat_insnlist drivers/comedi/comedi_fops.c:3208 [inline] comedi_compat_ioctl+0x810/0x990 drivers/comedi/comedi_fops.c:3273 __do_compat_sys_ioctl fs/ioctl.c:695 [inline] __se_compat_sys_ioctl fs/ioctl.c:638 [inline] __ia32_compat_sys_ioctl+0x242/0x370 fs/ioctl.c:638 do_syscall_32_irqs_on arch/x86/entry/syscall_32.c:83 [inline] ...
Timeline
ID reserved
By Linux
Published
- 5 months later
· 5 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (18 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 3fbfd2223a271426509830e6340c386a1054cfad – < 4836ba483a22ebd076c8faaf8293a7295fad4142
- affected 3fbfd2223a271426509830e6340c386a1054cfad – < 7141915bf0c41cb57d83cdbaf695b8c731b16b71
- affected 3fbfd2223a271426509830e6340c386a1054cfad – < f13895c03620933a58907e3250016f087e39b78c
- affected 3fbfd2223a271426509830e6340c386a1054cfad – < b975f91de5f8f63cf490f0393775cc795f8b0557
- affected 3fbfd2223a271426509830e6340c386a1054cfad – < f6e629dfe6f590091c662a87c9fcf118b1c1c7dc
- affected 3fbfd2223a271426509830e6340c386a1054cfad – < 573b07d2e3d473ee7eb625ef87519922cf01168d
- affected 3fbfd2223a271426509830e6340c386a1054cfad – < aac80e912de306815297a3b74f0426873ffa7dc3
- affected 3fbfd2223a271426509830e6340c386a1054cfad – < 0de7d9cd07a2671fa6089173bccc0b2afe6b93ee
- affected 5.8
- unaffected < 5.8
- unaffected 5.10.248 – ≤ 5.10.*
- unaffected 5.15.198 – ≤ 5.15.*
- unaffected 6.1.160 – ≤ 6.1.*
- unaffected 6.6.120 – ≤ 6.6.*
- unaffected 6.12.62 – ≤ 6.12.*
- unaffected 6.17.12 – ≤ 6.17.*
- unaffected 6.18.1 – ≤ 6.18.*
- unaffected 6.19 – ≤ *
References
References8
- https://git.kernel.org/stable/c/4836ba483a22ebd076c8faaf8293a7295fad4142 (opens in a new tab)
- https://git.kernel.org/stable/c/7141915bf0c41cb57d83cdbaf695b8c731b16b71 (opens in a new tab)
- https://git.kernel.org/stable/c/f13895c03620933a58907e3250016f087e39b78c (opens in a new tab)
- https://git.kernel.org/stable/c/b975f91de5f8f63cf490f0393775cc795f8b0557 (opens in a new tab)
- https://git.kernel.org/stable/c/f6e629dfe6f590091c662a87c9fcf118b1c1c7dc (opens in a new tab)
- https://git.kernel.org/stable/c/573b07d2e3d473ee7eb625ef87519922cf01168d (opens in a new tab)
- https://git.kernel.org/stable/c/aac80e912de306815297a3b74f0426873ffa7dc3 (opens in a new tab)
- https://git.kernel.org/stable/c/0de7d9cd07a2671fa6089173bccc0b2afe6b93ee (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-203740 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-68257)Record last updated .