VulnerabilityPublished 3 Nov 2026

CVE-2026-99259: Linux kernel · soc/tegra: pmc: Fix uninitialised clock rate

Affects Linux kernelSource CVE Database V5

Not known to be exploited : upgrade to c5c95dbdc9011a56359df4dc00be829bbcc0b036 or 43bc7d5707bbbf75e56db849b987193d6e866ec6 when convenient.

Data as of 3 Nov 2026, 11:58 UTC

Severity

Low

Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in c5c95dbdc9011a56359df4dc00be829bbcc0b036, 43bc7d5707bbbf75e56db849b987193d6e866ec6

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 3 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to c5c95dbdc9011a56359df4dc00be829bbcc0b036 or 43bc7d5707bbbf75e56db849b987193d6e866ec6.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 4d61f03426892b14d498e160be245edcb9dd8359, < c5c95dbdc9011a56359df4dc00be829bbcc0b036	Fixed in c5c95dbdc9011a56359df4dc00be829bbcc0b036
LinuxLinux	Affected ≥ 4d61f03426892b14d498e160be245edcb9dd8359, < 43bc7d5707bbbf75e56db849b987193d6e866ec6	Fixed in 43bc7d5707bbbf75e56db849b987193d6e866ec6
LinuxLinux	Affected =7.2	Fixed in–

AI-suggested

A fix is available and has been applied in the Linux kernel source (commits c5c95dbdc9011a56359df4dc00be829bbcc0b036 and 43bc7d5707bbbf75e56db849b987193d6e866ec6). Users and maintainers of affected Tegra devices should update to the fixed kernel version 7.2 or later containing these commits to resolve the issue.

Description

In the Linux kernel, the following vulnerability has been resolved: soc/tegra: pmc: Fix uninitialised clock rate For legacy 32-bit Tegra devices, the warning in the tegra_pmc_enter_suspend_mode() function is being triggered because the early_pmc->rate variable is never configured and hence, always 0. This issue started occurring after updating the PMC driver to create the PMC context dynamically which causes the 'rate' to be set in the new dynamic context, but missed updating the rate in the early PMC context. Fix this by initialising the early_pmc->rate variable for 32-bit Tegra devices when the rate for the PMC context is initialised. [treding@nvidia.com: move assignment to existing #ifdef block]

Impact

The vulnerability causes the early_pmc->rate variable to be zero, triggering warnings during suspend mode on legacy 32-bit Tegra devices. There is no indication of security impact such as privilege escalation or denial of service. The issue is primarily a correctness and stability concern in the kernel's power management code.

Summary

The Linux kernel contained a flaw in the soc/tegra PMC driver affecting legacy 32-bit Tegra devices. The early_pmc->rate variable was never initialized, causing warnings in the tegra_pmc_enter_suspend_mode() function. This occurred after the PMC driver was modified to create the PMC context dynamically, which set the rate in the new context but failed to update the early PMC context. The fix involves initializing early_pmc->rate when the PMC context rate is initialized, preventing the warning and ensuring correct operation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2026, 11:46 UTC

Technical details

References

Community reviews

Related threats