Kernel crash via invalid ROSE array index
Published Jan 13, 2026 · Updated Jan 13, 2026
Out-of-bounds array access in the Linux Kernel ROSE subsystem allows attackers to crash the kernel during network-device teardown. The rose_kill_by_device() function stores held sockets in a local array but dereferences array[cnt] on every iteration rather than the entry selected by the loop counter, producing an uninitialized or out-of-bounds socket pointer and leaking held references. Access to this path requires CAP_NET_ADMIN in the initial network namespace; unprivileged user namespaces cannot satisfy that requirement.
Summary
What happened
Out-of-bounds array access in the Linux Kernel ROSE subsystem allows attackers to crash the kernel during network-device teardown. The rose_kill_by_device() function stores held sockets in a local array but dereferences array[cnt] on every iteration rather than the entry selected by the loop counter, producing an uninitialized or out-of-bounds socket pointer and leaking held references. Access to this path requires CAP_NET_ADMIN in the initial network namespace; unprivileged user namespaces cannot satisfy that requirement.
The record
- CVE
- CVE-2025-71086
- Published
- Jan 13, 2026
- Updated
- Jan 13, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-129, T1499
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jan 13, 2026CVE publishedPublication date reported by the CVE source.
- Jan 13, 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=12e5a4719c99d7f4104e7e962393dfb8baa1c591
- Affected versionversion=3e0d1585799d8a991eba9678f297fd78d9f1846e <1418c12cd3bba79dc56b57b61c99efe40f579981
- Affected versionversion=64b8bc7d5f1434c636a40bdcfcd42b278d1714be <6595beb40fb0ec47223d3f6058ee40354694c8e4
- Affected versionversion=64b8bc7d5f1434c636a40bdcfcd42b278d1714be <92d900aac3a5721fb54f3328f1e089b44a861c38
- Affected versionversion=64b8bc7d5f1434c636a40bdcfcd42b278d1714be <b409ba9e1e63ccf3ab4cc061e33c1f804183543e
- Affected versionversion=6.7
- Affected versionversion=b10265532df7bc3666bc53261b7f03f0fd14b1c9
- Affected versionversion=bd7de4734535140fda33240c2335a07fdab6f88e
- Affected versionversion=c0e527c532a07556ca44642f5873b002c44da22c
- Affected versionversion=ffced26692f83212aa09d0ece0213b23cc2f611d <9f6185a32496834d6980b168cffcccc2d6b17280
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.
Weakness, pattern, technique
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