Skip to main content
VulnerabilityPublished Updated

CVE-2026-97963: Linux kernel · net: stmmac: initialize ptp_lock at probe time

Affects Linux kernelSource CVE Database V5

0

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

Data as of 26 Oct 2026, 12:55 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in ee33e424d4932c70f103b94a46b685923f236f65, b1986595cf827c38ff929e22fbc9ca8f76379306, 420315413b29635de1d4ea4142e410e6465260f3 +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 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
  • ≥ b60189e0392fa06348911077ef281eb2b1047b6a, < ee33e424d4932c70f103b94a46b685923f236f65
Fixed in
  • ee33e424d4932c70f103b94a46b685923f236f65
LinuxLinuxAffected
  • ≥ b60189e0392fa06348911077ef281eb2b1047b6a, < b1986595cf827c38ff929e22fbc9ca8f76379306
Fixed in
  • b1986595cf827c38ff929e22fbc9ca8f76379306
LinuxLinuxAffected
  • ≥ b60189e0392fa06348911077ef281eb2b1047b6a, < 420315413b29635de1d4ea4142e410e6465260f3
Fixed in
  • 420315413b29635de1d4ea4142e410e6465260f3
LinuxLinuxAffected
  • ≥ b60189e0392fa06348911077ef281eb2b1047b6a, < 0338c68e22abd2ee509ec2e32508a50896618c32
Fixed in
  • 0338c68e22abd2ee509ec2e32508a50896618c32
LinuxLinuxAffected
  • ≥ b60189e0392fa06348911077ef281eb2b1047b6a, < 79fb5bcc50996964e076dffbdc24b7d2c06bd957
Fixed in
  • 79fb5bcc50996964e076dffbdc24b7d2c06bd957
LinuxLinuxAffected
  • ≥ b60189e0392fa06348911077ef281eb2b1047b6a, < 25cc0096efba83b4e0e6fa50f03e9543b41e9d3d
Fixed in
  • 25cc0096efba83b4e0e6fa50f03e9543b41e9d3d

Description

In the Linux kernel, the following vulnerability has been resolved: net: stmmac: initialize ptp_lock at probe time priv->ptp_lock is only initialized in stmmac_ptp_register(), which runs during __stmmac_open(). However, the lock is also used while the interface is down and has never been opened: tc_taprio_configure() invokes the PTP gettime64() callback to compute the EST base time when offloading a TAPRIO schedule, and stmmac_get_time() takes priv->ptp_lock. Using an uninitialized rwlock is undefined behaviour. Move the rwlock_init() to __stmmac_dvr_probe(), together with the other private locks, so that ptp_lock is always valid regardless of the interface state.

References

Community reviews

Loading reviews…