---
id: "CVE-2026-99259"
kind: "vulnerability"
aliases: ["CVE-2026-99259"]
title: "Linux kernel: uninitialised clock rate on 32-bit Tegra suspend path"
severity: "unknown"
cvss: null
epss: null
exploited: false
status: "open"
category: "runtime"
products: []
ecosystems: []
tags: ["arm", "embedded", "linux-kernel", "runtime", "tegra"]
not_affected_if: ["64-bit-tegra", "non-tegra-hardware"]
published_at: "2026-11-03T12:17:32+00:00"
first_seen_at: "2026-11-03T12:20:39+00:00"
updated_at: "2026-11-03T12:22:47+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99259", "first_seen_at": "2026-11-03T12:20:39+00:00"}]
---

# Linux kernel: uninitialised clock rate on 32-bit Tegra suspend path

On legacy 32-bit NVIDIA Tegra devices, the Linux kernel's power management controller driver never sets a clock rate variable, so a warning fires during suspend. The description does not state any attacker-usable effect beyond this warning.

_Summary, check and fix written by a model from the sources; labelled as such._

## Timeline

- 2026-11-03T12:20:39+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-99259

## From the sources

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]

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_