# CVE-2026-68182: comedi: comedi_parport: deal with premature interrupt

> A premature interrupt in the comedi_parport driver causes a general protection fault, leading to a local denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** BELL-CVE-2026-68182, DEBIAN-CVE-2026-68182, GHSA-gw3j-wvcc-33mf, UBUNTU-CVE-2026-68182

## What is CVE-2026-68182?

CVE-2026-68182 is a vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2026-68182?


## How do I fix CVE-2026-68182?

Apply the vendor's patch.

## Is CVE-2026-68182 being exploited?

There is no known exploitation of CVE-2026-68182 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68182 and fix it if it is affected.

What it is: CVE-2026-68182 is a vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-68182 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68182/ (Markdown: https://insights.sbomify.com/CVE-2026-68182/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68182
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68182
- OSV: https://osv.dev/vulnerability/CVE-2026-68182

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68182/
Summaries are generated and may contain mistakes; the official description above is the record.