CVE-2026-68182

comedi: comedi_parport: deal with premature interrupt

N/A
Published: August 10, 2026 at 11:59 AM UTC
Updated: August 19, 2026 at 05:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.29 ≤ v < 5.10.2652.6.29 ≤ v < 5.15.2162.6.29 ≤ v < 6.1.1832.6.29 ≤ v < 6.12.1012.6.29 ≤ v < 6.18.422.6.29 ≤ v < 6.6.1482.6.29 ≤ v < 7.1.62.6.29 ≤ v < 7.22.6.29241ab6ad7108e51c67881f7881c5e46f0400cdb1
Vendor states this is fixed in 086a9ae3c5df63ec11033a8c0b3f6a1fd295ddd1 (fixed)
Vendor states this is fixed in 17221216ae8ce6a24e8a4e787382e3ebc81b88a8 (fixed)
Vendor states this is fixed in 48ef18e5eb6b8a9c546038b2ab89a841fcd97fe7 (fixed)
Vendor states this is fixed in 5d059ce0e6a2f6f8b97273499d47b8f917097b48 (fixed)
Vendor states this is fixed in 6ed34611e569fc1a1169905c5228fd0eb2806c1b (fixed)
Vendor states this is fixed in a88b25db815ff6edace81b0bb0f4a201133bd215 (fixed)
Vendor states this is fixed in b061bb4dca49fd93063359d3805387235818778c (fixed)
Vendor states this is fixed in cf26dd2d841583c54a87005c4934b92fddb930c3 (fixed)
Vendor states this is fixed in 2.6.29 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card