Service interruption via premature RCU callback code unloading
Published Sep 17, 2026 · Updated Sep 17, 2026
Use-after-unload in Linux IPoIB allows local users to interrupt kernel operation via a race during module teardown. ipoib_cleanup_module() and the ipoib_init_module() failure path omit RCU callback draining, allowing ib_ipoib code to continue executing after unload. Exposure requires IPoIB callbacks during teardown or failed client registration; published sources do not specify whether interruption is a crash or hang.
Summary
What happened
Use-after-unload in Linux IPoIB allows local users to interrupt kernel operation via a race during module teardown. ipoib_cleanup_module() and the ipoib_init_module() failure path omit RCU callback draining, allowing ib_ipoib code to continue executing after unload. Exposure requires IPoIB callbacks during teardown or failed client registration; published sources do not specify whether interruption is a crash or hang.
The record
- CVE
- CVE-2026-93108
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 2026Record 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=3.6
- Affected versionversion=b63b70d8774175b6f8393c495fe455f0fba55ce1 <24ce944721dcd92ae62e7a448d770e2a3e79f5fd
- Affected versionversion=b63b70d8774175b6f8393c495fe455f0fba55ce1 <2b3330cfc097db2d31f47ad09261967630270d66
- Affected versionversion=b63b70d8774175b6f8393c495fe455f0fba55ce1 <31b7c700670830a0e8a4cdcd451c88a13cc5dc48
- Affected versionversion=b63b70d8774175b6f8393c495fe455f0fba55ce1 <4a6dc313f9661f80e4ed43461d7ed5615c2450ca
- Affected versionversion=b63b70d8774175b6f8393c495fe455f0fba55ce1 <7bc08d7f9338c9f9c09965e5d020591c793a80cb
- Affected versionversion=b63b70d8774175b6f8393c495fe455f0fba55ce1 <8dc5ffcb8efcc01e44dd1ebc490eaae72de3fadf
- Affected versionversion=b63b70d8774175b6f8393c495fe455f0fba55ce1 <bb9c23733a0c50e136bd40c27cb60023cc58e22c
- Affected versionversion=b63b70d8774175b6f8393c495fe455f0fba55ce1 <d8917353966d1d5a486437dd0dd68a2cf8ecb136
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started