From this webpage screenshot, the following key information about the vulnerability can be obtained: Issue Description: When handling the event, the bridge driver may trigger a deferred notification, leading to recursive notifications. This causes the read-write semaphore to be acquired twice for reading, triggering a lock warning. Root Cause: The recursive notifications result in the semaphore being acquired multiple times, specifically occurring during the call to . Solution: Convert the blocking notifier chain into an atomic notifier chain, similar to the notifier chain. Protect the chain with the RTNL mutex, acquiring it when modifying the chain. Events are always notified to listeners under the RTNL mutex, and an assertion has been added in to ensure this rule is not violated in the future. Related Code and Logs: - Specific lock warning log: Commit Information: - Author: Amit Cohen - Committer: Greg Kroah-Hartman - Commit Time: 2025-03-05 14:15:09 +0200 - Commit Hash: a597d4b75669ec82c72cbee9fe875a15d04b35b2b This information indicates a locking issue related to semaphores and notifier chains in the kernel, which has been resolved through code changes.