https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 11:29:34 +0000 https://vulnerability.circl.lu/vuln/cve-2021-47583 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>media: mxl111sf: change mutex_init() location</p> <p>Syzbot reported, that mxl111sf_ctrl_msg() uses uninitialized mutex. The problem was in wrong mutex_init() location.</p> <p>Previous mutex_init(&amp;state-&gt;msg_lock) call was in -&gt;init() function, but dvb_usbv2_init() has this order of calls:</p> <p>dvb_usbv2_init() dvb_usbv2_adapter_init() dvb_usbv2_adapter_frontend_init() props-&gt;frontend_attach()</p> <p>props-&gt;init()</p> <p>Since mxl111sf_* devices call mxl111sf_ctrl_msg() in -&gt;frontend_attach() internally we need to initialize state-&gt;msg_lock before frontend_attach(). To achieve it, -&gt;probe() call added to all mxl111sf_* devices, which will simply initiaize mutex.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>media: mxl111sf: change mutex_init() location</p> <p>Syzbot reported, that mxl111sf_ctrl_msg() uses uninitialized mutex. The problem was in wrong mutex_init() location.</p> <p>Previous mutex_init(&amp;state-&gt;msg_lock) call was in -&gt;init() function, but dvb_usbv2_init() has this order of calls:</p> <p>dvb_usbv2_init() dvb_usbv2_adapter_init() dvb_usbv2_adapter_frontend_init() props-&gt;frontend_attach()</p> <p>props-&gt;init()</p> <p>Since mxl111sf_* devices call mxl111sf_ctrl_msg() in -&gt;frontend_attach() internally we need to initialize state-&gt;msg_lock before frontend_attach(). To achieve it, -&gt;probe() call added to all mxl111sf_* devices, which will simply initiaize mutex.</p> https://vulnerability.circl.lu/vuln/cve-2021-47583