Network-device removal hang via J1939 activation race
Published Jan 31, 2026 · Updated Jan 31, 2026
Race condition in the CAN J1939 transport of Linux Kernel allows local users to hang network-device unregistration during session activation. j1939_session_activate() accepts a session after j1939_cancel_active_session() finishes because it does not check the device registration state while holding the session-list lock. Reaching the flaw requires local access to the J1939 interface; the resulting retained device reference blocks removal and affects availability only.
Summary
What happened
Race condition in the CAN J1939 transport of Linux Kernel allows local users to hang network-device unregistration during session activation. j1939_session_activate() accepts a session after j1939_cancel_active_session() finishes because it does not check the device registration state while holding the session-list lock. Reaching the flaw requires local access to the J1939 interface; the resulting retained device reference blocks removal and affects availability only.
The record
- CVE
- CVE-2025-71182
- Published
- Jan 31, 2026
- Updated
- Jan 31, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 31, 2026CVE publishedPublication date reported by the CVE source.
- Jan 31, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <46ca9dc978923c5e1247a9e9519240ba7ace413c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5d5602236f5db19e8b337a2cd87a90ace5ea776d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <78d87b72cebe2a993fd5b017e9f14fb6278f2eae
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <79dd3f1d9dd310c2af89b09c71f34d93973b200f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ba6f0d1832eeb5eb3a6dc5cb30e0f720b3cb3536
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c3a4316e3c746af415c0fd6c6d489ad13f53714d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ebb0dfd718dd31c8d3600612ca4b7207ec3d923a
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