Bug 2541153 (CVE-2026-97963) - CVE-2026-97963 kernel: net: stmmac: initialize ptp_lock at probe time
Summary: CVE-2026-97963 kernel: net: stmmac: initialize ptp_lock at probe time
Keywords:
Status: NEW
Alias: CVE-2026-97963
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-25 10:52 UTC by OSIDB Bzimport
Modified: 2026-09-30 04:08 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-25 10:52:48 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.