In the Linux kernel, the following vulnerability has been resolved: eth: alx: take rtnllock on resume Zbynek reports that alx trips an rtnl assertion on resume: RTNL: assertion failed at net/core/dev.c (2891) RIP: 0010:netifsetrealnumtxqueues+0x1ac/0x1c0 Call Trace: <TASK> _alxopen+0x230/0x570 [alx] alxresume+0x54/0x80 [alx] ? pcilegacyresume+0x80/0x80 dpmruncallback+0x4a/0x150 deviceresume+0x8b/0x190 asyncresume+0x19/0x30 asyncrunentryfn+0x30/0x130 processonework+0x1e5/0x3b0 indeed the driver does not hold rtnl_lock during its internal close and re-open functions during suspend/resume. Note that this is not a huge bug as the driver implements its own locking, and does not implement changing the number of queues, but we need to silence the splat.