CVE-2026-68182: comedi: comedi_parport: deal with premature interrupt
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 086a9ae3c5df63ec11033a8c0b3f6a1fd295ddd1, 17221216ae8ce6a24e8a4e787382e3ebc81b88a8, 48ef18e5eb6b8a9c546038b2ab89a841fcd97fe7; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 086a9ae3c5df63ec11033a8c0b3f6a1fd295ddd1, 17221216ae8ce6a24e8a4e787382e3ebc81b88a8, 48ef18e5eb6b8a9c546038b2ab89a841fcd97fe7; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-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: comedi: comedi_parport: deal with premature interrupt Syzbot reported a general protection fault in `comedi_get_is_subdevice_running()`, which was called from the interrupt handler `parport_interrupt()` in the "comedi_parport" driver, but it does not currently have a C reproducer for the problem. It's probably due to a premature interrupt for one of two reasons: 1. The driver sets up the interrupt handler before the comedi subdevices used by the interrupt handler have been allocated, but does not disable the interrupt in the parallel port's CTRL register first. 2. The driver uses a user-supplied I/O port base address which Syzbot would have supplied, but it might not be backed by real parallel port hardware. Change the initialization order in the driver's comedi "attach" handler (`parport_attach()`) so that the hardware registers are initialized before the interrupt handler is requested. This should prevent premature interrupts occurring for real hardware. Also add a test to the interrupt handler to ensure the comedi device is fully attached and return early if it isn't.
- Published
- Aug 10, 2026
- Updated
- Aug 19, 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
- 2.6.29affected
- 241ab6ad7108e51c67881f7881c5e46f0400cdb1 and later · before 6ed34611e569fc1a1169905c5228fd0eb2806c1baffected · git
- 241ab6ad7108e51c67881f7881c5e46f0400cdb1 and later · before 48ef18e5eb6b8a9c546038b2ab89a841fcd97fe7affected · git
- 241ab6ad7108e51c67881f7881c5e46f0400cdb1 and later · before a88b25db815ff6edace81b0bb0f4a201133bd215affected · git
- 241ab6ad7108e51c67881f7881c5e46f0400cdb1 and later · before b061bb4dca49fd93063359d3805387235818778caffected · git
- 241ab6ad7108e51c67881f7881c5e46f0400cdb1 and later · before 086a9ae3c5df63ec11033a8c0b3f6a1fd295ddd1affected · git
- 241ab6ad7108e51c67881f7881c5e46f0400cdb1 and later · before cf26dd2d841583c54a87005c4934b92fddb930c3affected · git
- 241ab6ad7108e51c67881f7881c5e46f0400cdb1 and later · before 5d059ce0e6a2f6f8b97273499d47b8f917097b48affected · git
- 241ab6ad7108e51c67881f7881c5e46f0400cdb1 and later · before 17221216ae8ce6a24e8a4e787382e3ebc81b88a8affected · git
- before 2.6.29not 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.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.101-1~deb12u1 | 6.12.101-1~deb12u1 |
| Debian:13 | linux | before 6.12.101-1 | 6.12.101-1 |
| Debian:14 | linux | before 7.1.6-1 | 7.1.6-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-2026-68180Aug 10, 2026 · intel_th: fix MSC output device reference leak0Monitor
- ← EarlierCVE-2026-68181Aug 10, 2026 · mei: bus: access mei_device under device_lock on cleanup0Monitor
- Later →CVE-2026-68183Aug 10, 2026 · firmware: stratix10-svc: fix memory leaks and list corruption bugs0Monitor
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 | 086a9ae3c5df63ec11033a8c0b3f6a1fd295ddd1 | Vendor (CNA) |
| Linux Linux | 17221216ae8ce6a24e8a4e787382e3ebc81b88a8 | Vendor (CNA) |
| Linux Linux | 48ef18e5eb6b8a9c546038b2ab89a841fcd97fe7 | Vendor (CNA) |
| Linux Linux | 5d059ce0e6a2f6f8b97273499d47b8f917097b48 | Vendor (CNA) |
| Linux Linux | 6ed34611e569fc1a1169905c5228fd0eb2806c1b | Vendor (CNA) |
| Linux Linux | a88b25db815ff6edace81b0bb0f4a201133bd215 | Vendor (CNA) |
| Linux Linux | b061bb4dca49fd93063359d3805387235818778c | Vendor (CNA) |
| Linux Linux | cf26dd2d841583c54a87005c4934b92fddb930c3 | Vendor (CNA) |
| azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 | 6.6.150.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · 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.
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)
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/17221216ae8ce6a24e8a4e787382e3ebc81b88a8
- git.kernel.org/stable/c/48ef18e5eb6b8a9c546038b2ab89a841fcd97fe7
- git.kernel.org/stable/c/5d059ce0e6a2f6f8b97273499d47b8f917097b48
- git.kernel.org/stable/c/6ed34611e569fc1a1169905c5228fd0eb2806c1b
- git.kernel.org/stable/c/a88b25db815ff6edace81b0bb0f4a201133bd215
- git.kernel.org/stable/c/b061bb4dca49fd93063359d3805387235818778c
- git.kernel.org/stable/c/cf26dd2d841583c54a87005c4934b92fddb930c3
Vendor advisories and official records. Exploit/PoC links are deliberately left out.