Kernel oops via incompatible IRQ locking
Published Sep 16, 2025 · Updated Sep 16, 2025
Improper locking in affected Linux kernels allows local users to trigger a kernel oops through an rtl8723bs wireless join timeout. _rtw_join_timeout_handler() keeps IRQs disabled with spin_lock_irq() while rtw_do_join() releases scanned_queue.lock with spin_unlock_bh(), re-enabling softirqs where lockdep requires IRQs enabled. Reachability requires the staging r8723bs driver and its join-timeout path; the documented consequence is an oops with no confidentiality or integrity impact.
Summary
What happened
Improper locking in affected Linux kernels allows local users to trigger a kernel oops through an rtl8723bs wireless join timeout. _rtw_join_timeout_handler() keeps IRQs disabled with spin_lock_irq() while rtw_do_join() releases scanned_queue.lock with spin_unlock_bh(), re-enabling softirqs where lockdep requires IRQs enabled. Reachability requires the staging r8723bs driver and its join-timeout path; the documented consequence is an oops with no confidentiality or integrity impact.
The record
- CVE
- CVE-2023-53281
- Published
- Sep 16, 2025
- Updated
- Sep 16, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 16, 2025CVE publishedPublication date reported by the CVE source.
- Sep 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=041879b12ddb0c6c83ed9c0bdd10dc82a056f2fc <215792eda008f6a1e7ed9d77fa20d582d22bb114
- Affected versionversion=041879b12ddb0c6c83ed9c0bdd10dc82a056f2fc <2a50e44a66d268ee5db3d177f1fdc1503dbce6e7
- Affected versionversion=041879b12ddb0c6c83ed9c0bdd10dc82a056f2fc <4ab1bace1dd3875371b481ef4301c4671bddea22
- Affected versionversion=041879b12ddb0c6c83ed9c0bdd10dc82a056f2fc <dc327e87c6d9bfd9ee08e76396b3c0ba848ec554
- Affected versionversion=1f6c99b94ca3caad346876b3e22e3ca3d25bc8ee
- Affected versionversion=5.19
- Affected versionversion=ae60744d5fad840b9d056d35b4b652d95e755846 <209850f17717a3b5cc558578bef5631ac7045539
- Affected versionversion=eca9748d9267a38d532464e3305a38629e9c35a9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo