comedi: multiq3: sanitize config options in multiq3_attach()
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 049f14557450351750f929ebfff36d849511e132, 4cde9a7e025cc09b88097c70606f6b30c22880f4, 543f4c380c2e1f35e60528df7cb54705cda7fee3.
Low priority for now. Upgrade to Linux Linux 049f14557450351750f929ebfff36d849511e132, 4cde9a7e025cc09b88097c70606f6b30c22880f4, 543f4c380c2e1f35e60528df7cb54705cda7fee3 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
In the Linux kernel, the following vulnerability has been resolved: comedi: multiq3: sanitize config options in multiq3_attach() Syzbot identified an issue [1] in multiq3_attach() that induces a task timeout due to open() or COMEDI_DEVCONFIG ioctl operations, specifically, in the case of multiq3 driver. This problem arose when syzkaller managed to craft weird configuration options used to specify the number of channels in encoder subdevice. If a particularly great number is passed to s->n_chan in multiq3_attach() via it->options[2], then multiple calls to multiq3_encoder_reset() at the end of driver-specific attach() method will be running for minutes, thus blocking tasks and affected devices as well. While this issue is most likely not too dangerous for real-life devices, it still makes sense to sanitize configuration inputs. Enable a sensible limit on the number of encoder chips (4 chips max, each with 2 channels) to stop this behaviour from manifesting. [1] Syzbot crash: INFO: task syz.2.19:6067 blocked for more than 143 seconds. ... Call Trace: <TASK> context_switch kernel/sched/core.c:5254 [inline] __schedule+0x17c4/0x4d60 kernel/sched/core.c:6862 __schedule_loop kernel/sched/core.c:6944 [inline] schedule+0x165/0x360 kernel/sched/core.c:6959 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:7016 __mutex_lock_common kernel/locking/mutex.c:676 [inline] __mutex_lock+0x7e6/0x1350 kernel/locking/mutex.c:760 comedi_open+0xc0/0x590 drivers/comedi/comedi_fops.c:2868 chrdev_open+0x4cc/0x5e0 fs/char_dev.c:414 do_dentry_open+0x953/0x13f0 fs/open.c:965 vfs_open+0x3b/0x340 fs/open.c:1097 ...
- Published
- Dec 16, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 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.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
- 2.6.30affected
- 77e01cdbad5175f56027fd6fae00bd0fc175651a and later · before f9ff87aac7b37d462246c46d28912d382a8e2ea6affected · git
- 77e01cdbad5175f56027fd6fae00bd0fc175651a and later · before 4cde9a7e025cc09b88097c70606f6b30c22880f4affected · git
- 77e01cdbad5175f56027fd6fae00bd0fc175651a and later · before ad7ed3c9c7b8408e8612697bc43a5441fe386c71affected · git
- 77e01cdbad5175f56027fd6fae00bd0fc175651a and later · before 049f14557450351750f929ebfff36d849511e132affected · git
- 77e01cdbad5175f56027fd6fae00bd0fc175651a and later · before 8952bc1973cd54158c35e06bfb8c29ace7375a48affected · git
- 77e01cdbad5175f56027fd6fae00bd0fc175651a and later · before 8dc2f02d3bada9247f00bfd2e5f61f68c389a0a3affected · git
- 77e01cdbad5175f56027fd6fae00bd0fc175651a and later · before 543f4c380c2e1f35e60528df7cb54705cda7fee3affected · git
- 77e01cdbad5175f56027fd6fae00bd0fc175651a and later · before f24c6e3a39fa355dabfb684c9ca82db579534e72affected · 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.2-1.1 | 6.18.2-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
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
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 | 049f14557450351750f929ebfff36d849511e132 | Vendor (CNA) |
| Linux Linux | 4cde9a7e025cc09b88097c70606f6b30c22880f4 | Vendor (CNA) |
| Linux Linux | 543f4c380c2e1f35e60528df7cb54705cda7fee3 | Vendor (CNA) |
| Linux Linux | 8952bc1973cd54158c35e06bfb8c29ace7375a48 | Vendor (CNA) |
| Linux Linux | 8dc2f02d3bada9247f00bfd2e5f61f68c389a0a3 | Vendor (CNA) |
| Linux Linux | ad7ed3c9c7b8408e8612697bc43a5441fe386c71 | Vendor (CNA) |
| Linux Linux | f24c6e3a39fa355dabfb684c9ca82db579534e72 | Vendor (CNA) |
| Linux Linux | f9ff87aac7b37d462246c46d28912d382a8e2ea6 | Vendor (CNA) |
| debian:linux | 6.1.162-1 · Debian:12 | Package registry (OSV) |
| opensuse:kernel-source | 6.18.2-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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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/4cde9a7e025cc09b88097c70606f6b30c22880f4
- git.kernel.org/stable/c/543f4c380c2e1f35e60528df7cb54705cda7fee3
- git.kernel.org/stable/c/8952bc1973cd54158c35e06bfb8c29ace7375a48
- git.kernel.org/stable/c/8dc2f02d3bada9247f00bfd2e5f61f68c389a0a3
- git.kernel.org/stable/c/ad7ed3c9c7b8408e8612697bc43a5441fe386c71
- git.kernel.org/stable/c/f24c6e3a39fa355dabfb684c9ca82db579534e72
- git.kernel.org/stable/c/f9ff87aac7b37d462246c46d28912d382a8e2ea6
Vendor advisories and official records. Exploit/PoC links are deliberately left out.