Description
In the Linux kernel, the following vulnerability has been resolved: eth: alx: take rtnl_lock on resume Zbynek reports that alx trips an rtnl assertion on resume: RTNL: assertion failed at net/core/dev.c (2891) RIP: 0010:netif_set_real_num_tx_queues+0x1ac/0x1c0 Call Trace: <TASK> __alx_open+0x230/0x570 [alx] alx_resume+0x54/0x80 [alx] ? pci_legacy_resume+0x80/0x80 dpm_run_callback+0x4a/0x150 device_resume+0x8b/0x190 async_resume+0x19/0x30 async_run_entry_fn+0x30/0x130 process_one_work+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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
4a5fe57e775188be96359a1934501be45fe5f705 to < 6f1991a940b90753b34570f093a21dba366e8cc0affected4a5fe57e775188be96359a1934501be45fe5f705 to < a845a0c4bdece2c0073ecea2fca7c4d5f0550f78affected4a5fe57e775188be96359a1934501be45fe5f705 to < c0323c0fd07804d5874699e93f935cda0d989c67affected4a5fe57e775188be96359a1934501be45fe5f705 to < 6ad1c94e1e7e374d88f0cfd77936dddb8339aabaaffected
Linux Linux
Default version status: affected
5.14affected0 to < 5.14unaffected5.15.75 to ≤ 5.15.*unaffected5.19.17 to ≤ 5.19.*unaffected6.0.3 to ≤ 6.0.*unaffected6.1 to ≤ *unaffected