https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 09:32:27 +0000 https://vulnerability.circl.lu/vuln/cve-2025-68332 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>comedi: c6xdigio: Fix invalid PNP driver unregistration</p> <p>The Comedi low-level driver &#34;c6xdigio&#34; seems to be for a parallel port connected device. When the Comedi core calls the driver&#39;s Comedi &#34;attach&#34; handler `c6xdigio_attach()` to configure a Comedi to use this driver, it tries to enable the parallel port PNP resources by registering a PNP driver with `pnp_register_driver()`, but ignores the return value. (The `struct pnp_driver` it uses has only the `name` and `id_table` members filled in.) The driver&#39;s Comedi &#34;detach&#34; handler `c6xdigio_detach()` unconditionally unregisters the PNP driver with `pnp_unregister_driver()`.</p> <p>It is possible for `c6xdigio_attach()` to return an error before it calls `pnp_register_driver()` and it is possible for the call to `pnp_register_driver()` to return an error (that is ignored). In both cases, the driver should not be calling `pnp_unregister_driver()` as it does in `c6xdigio_detach()`. (Note that `c6xdigio_detach()` will be called by the Comedi core if `c6xdigio_attach()` returns an error, or if the Comedi core decides to detach the Comedi device from the driver for some other reason.)</p> <p>The unconditional call to `pnp_unregister_driver()` without a previous successful call to `pnp_register_driver()` will cause `driver_unregister()` to issue a warning &#34;Unexpected driver unregister!&#34;. This was detected by Syzbot [1].</p> <p>Also, the PNP driver registration and unregistrati…</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>comedi: c6xdigio: Fix invalid PNP driver unregistration</p> <p>The Comedi low-level driver &#34;c6xdigio&#34; seems to be for a parallel port connected device. When the Comedi core calls the driver&#39;s Comedi &#34;attach&#34; handler `c6xdigio_attach()` to configure a Comedi to use this driver, it tries to enable the parallel port PNP resources by registering a PNP driver with `pnp_register_driver()`, but ignores the return value. (The `struct pnp_driver` it uses has only the `name` and `id_table` members filled in.) The driver&#39;s Comedi &#34;detach&#34; handler `c6xdigio_detach()` unconditionally unregisters the PNP driver with `pnp_unregister_driver()`.</p> <p>It is possible for `c6xdigio_attach()` to return an error before it calls `pnp_register_driver()` and it is possible for the call to `pnp_register_driver()` to return an error (that is ignored). In both cases, the driver should not be calling `pnp_unregister_driver()` as it does in `c6xdigio_detach()`. (Note that `c6xdigio_detach()` will be called by the Comedi core if `c6xdigio_attach()` returns an error, or if the Comedi core decides to detach the Comedi device from the driver for some other reason.)</p> <p>The unconditional call to `pnp_unregister_driver()` without a previous successful call to `pnp_register_driver()` will cause `driver_unregister()` to issue a warning &#34;Unexpected driver unregister!&#34;. This was detected by Syzbot [1].</p> <p>Also, the PNP driver registration and unregistrati…</p> https://vulnerability.circl.lu/vuln/cve-2025-68332