Skip to main content
VulnerabilityPublished Updated

CVE-2025-71182: Linux kernel · Race Condition

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in ebb0dfd718dd31c8d3600612ca4b7207ec3d923a : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:18 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-06-10.

Patch
Available – fixed in ebb0dfd718dd31c8d3600612ca4b7207ec3d923a, c3a4316e3c746af415c0fd6c6d489ad13f53714d, ba6f0d1832eeb5eb3a6dc5cb30e0f720b3cb3536 +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 9d71dd0c70099914fcd063135da3c580865e924c, < ebb0dfd718dd31c8d3600612ca4b7207ec3d923a
Fixed in
  • ebb0dfd718dd31c8d3600612ca4b7207ec3d923a
LinuxLinuxAffected
  • ≥ 9d71dd0c70099914fcd063135da3c580865e924c, < c3a4316e3c746af415c0fd6c6d489ad13f53714d
Fixed in
  • c3a4316e3c746af415c0fd6c6d489ad13f53714d
LinuxLinuxAffected
  • ≥ 9d71dd0c70099914fcd063135da3c580865e924c, < ba6f0d1832eeb5eb3a6dc5cb30e0f720b3cb3536
Fixed in
  • ba6f0d1832eeb5eb3a6dc5cb30e0f720b3cb3536
LinuxLinuxAffected
  • ≥ 9d71dd0c70099914fcd063135da3c580865e924c, < 79dd3f1d9dd310c2af89b09c71f34d93973b200f
Fixed in
  • 79dd3f1d9dd310c2af89b09c71f34d93973b200f
LinuxLinuxAffected
  • ≥ 9d71dd0c70099914fcd063135da3c580865e924c, < 78d87b72cebe2a993fd5b017e9f14fb6278f2eae
Fixed in
  • 78d87b72cebe2a993fd5b017e9f14fb6278f2eae
LinuxLinuxAffected
  • ≥ 9d71dd0c70099914fcd063135da3c580865e924c, < 46ca9dc978923c5e1247a9e9519240ba7ace413c
Fixed in
  • 46ca9dc978923c5e1247a9e9519240ba7ace413c

Description

In the Linux kernel, the following vulnerability has been resolved: can: j1939: make j1939_session_activate() fail if device is no longer registered syzbot is still reporting unregister_netdevice: waiting for vcan0 to become free. Usage count = 2 even after commit 93a27b5891b8 ("can: j1939: add missing calls in NETDEV_UNREGISTER notification handler") was added. A debug printk() patch found that j1939_session_activate() can succeed even after j1939_cancel_active_session() from j1939_netdev_notify(NETDEV_UNREGISTER) has completed. Since j1939_cancel_active_session() is processed with the session list lock held, checking ndev->reg_state in j1939_session_activate() with the session list lock held can reliably close the race window.

References

Community reviews

Loading reviews…