fbnic: close fw_log race between users and teardown
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 223cfef4812bdfa5ac5c1aa761cdba03cfe2c9cd, Kernel 5f10ab3643c58a22fbaee92c4701b00fcb4a465d and Kernel ee5492fd88cfc079c19fbeac78e9e53b7f6c04f3.
In the Linux kernel, the following vulnerability has been resolved: fbnic: close fw_log race between users and teardown Fixes a theoretical race on fw_log between the teardown path and fw_log write functions. fw_log is written inside fbnic_fw_log_write() and can be reached from the mailbox handler fbnic_fw_msix_intr(), but fw_log is freed before IRQ/MBX teardown during cleanup, resulting in a potential data race of dereferencing a freed/null variable. Possible Interleaving Scenario: CPU0: fbnic_fw_msix_intr() // Entry fbnic_fw_log_write() if (fbnic_fw_log_ready()) // true ... preempt ... CPU1: fbnic_remove() // Entry fbnic_fw_log_free() vfree(log->data_start); log->data_start = NULL; CPU0: continues, walks log->entries or writes to log->data_start The initialization also has an incorrect order problem, as the fw_log is currently allocated after MBX setup during initialization. Fix the problems by adjusting the synchronization order to put initialization in place before the mailbox is enabled, and not cleared until after the mailbox has been disabled.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.17, >=ecc53b1b46c892d2e3cf3cf4393b6d219dc4ae3f <223cfef4812bdfa5ac5c1aa761cdba03cfe2c9cd, >=ecc53b1b46c892d2e3cf3cf4393b6d219dc4ae3f <5f10ab3643c58a22fbaee92c4701b00fcb4a465d, >=ecc53b1b46c892d2e3cf3cf4393b6d219dc4ae3f <ee5492fd88cfc079c19fbeac78e9e53b7f6c04f3 | 223cfef4812bdfa5ac5c1aa761cdba03cfe2c9cd, 5f10ab3643c58a22fbaee92c4701b00fcb4a465d, ee5492fd88cfc079c19fbeac78e9e53b7f6c04f3 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket