CVE-2026-63942

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> parport: Fix race between port and client registration<br /> <br /> The parport subsystem registers port devices before they are fully<br /> initialised, resulting in a race condition where client drivers such<br /> as lp can attach to ports that are not completely initialised or even<br /> being torn down.<br /> <br /> When the port and client drivers are built as modules and loaded<br /> around the same time during boot, this occasionally results in a<br /> crash. I was able to make this happen reliably in a VM with a<br /> PC-style parallel port by patching parport_pc to fail probing:<br /> <br /> &gt; --- a/drivers/parport/parport_pc.c<br /> &gt; +++ b/drivers/parport/parport_pc.c<br /> &gt; @@ -2069,7 +2069,7 @@ static struct parport *__parport_pc_probe_port(unsigned long int base,<br /> &gt; if (!p)<br /> &gt; goto out3;<br /> &gt;<br /> &gt; - base_res = request_region(base, 3, p-&gt;name);<br /> &gt; + base_res = NULL;<br /> &gt; if (!base_res)<br /> &gt; goto out4;<br /> &gt;<br /> <br /> and then running:<br /> <br /> while true; do<br /> modprobe lp &amp; modprobe parport_pc<br /> wait<br /> rmmod lp parport_pc<br /> done<br /> <br /> for a few seconds.<br /> <br /> In the long term I think port registration should be changed to put<br /> the call to device_add() inside parport_announce_port(), but since the<br /> latter currently cannot fail this will require changing all port<br /> drivers.<br /> <br /> For now, add a flag to indicate whether a port has been "announced"<br /> and only try to attach client drivers to ports when the flag is set.