VulnerabilityPublished 3 Nov 2026

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

Source GCVE Database

Authoritative record:CVE-2026-99259· Low

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

Data as of 3 Nov 2026, 13:15 UTC

Severity

Low

Rated by Threat Radar · 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.

ghsa-mrwj-wrmj-995m

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 has been implemented to initialize the early_pmc->rate variable properly. Users should apply the updated Linux kernel version containing this fix once it is available. No additional mitigation steps are indicated.

Description

A vulnerability in the Linux kernel's Tegra PMC driver caused the early_pmc->rate variable to remain uninitialized for legacy 32-bit Tegra devices, leading to a warning during suspend mode. This was due to the dynamic creation of the PMC context missing initialization of the early PMC context's rate. The issue has been fixed by properly initializing the early_pmc->rate variable.

Impact

The vulnerability causes a warning due to an uninitialized clock rate variable in the Tegra PMC driver during suspend mode on legacy 32-bit Tegra devices. There is no indication of security impact such as privilege escalation, denial of service, or information disclosure. No known exploits in the wild have been reported.

Summary

The Linux kernel's soc/tegra PMC driver had a flaw where the early_pmc->rate variable was never initialized for legacy 32-bit Tegra devices, causing warnings in the tegra_pmc_enter_suspend_mode() function. This problem arose after the PMC driver was updated to create the PMC context dynamically, which set the rate in the new context but failed to update the early PMC context. The fix involved initializing the early_pmc->rate variable when the PMC context rate is initialized for these devices.

References

Community reviews

Loading reviews…