# CVE-2026-99259: Linux kernel PMC uninitialized clock rate in 32-bit Tegra

Source: https://junglewise.ai/threats/cve-2026-99259-in-the-linux-kernel-the-following-vulnerability-has-been-resolved  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-03. Updated: 2026-11-03  
License: CC BY 4.0 with a link back

CVE-2026-99259 · Severity: info · Published 2026-11-03

The Linux kernel's Power Management Controller (PMC) driver for legacy 32-bit Tegra devices fails to initialize a clock rate variable, causing warning messages during system suspend. While not exploitable as a security vulnerability, this fix addresses a stability issue affecting older Tegra-based systems.

Technologies: [Linux Kernel](https://junglewise.ai/threats/technologies/kernel). Vendors: [Linux](https://junglewise.ai/threats/vendors/linux).

## Quick answers

**Is CVE-2026-99259 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-99259 being exploited in the wild.

**How severe is CVE-2026-99259?** Informational severity, published 3 November 2026.

**Which products and versions are affected?** Linux Kernel versions containing commit 4d61f0342689 and before fix commit c5c95dbdc9011a56359df4dc00be829bbcc0b036.

**Is there a fix for CVE-2026-99259?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-99259 attacked?** It is attacked with local access, in an operating system.

**Am I affected by CVE-2026-99259?** Check whether you run Linux Kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

An uninitialized early_pmc->rate variable in the tegra_pmc_probe() function causes the tegra_pmc_enter_suspend_mode() function to trigger a warning when called on 32-bit Tegra devices. The issue was introduced when the PMC driver was refactored to create the PMC context dynamically; the rate was set in the new dynamic context but not copied to the legacy early PMC context. The fix is a single-line assignment that copies the rate value to the early context during initialization.

## Affected products

- Linux kernel versions containing commit 4d61f0342689 and before fix commit c5c95dbdc9011a56359df4dc00be829bbcc0b036

## Timeline

- 2026-11-03: disclosed

## References

- [https://git.kernel.org/stable/c/43bc7d5707bbbf75e56db849b987193d6e866ec6](https://git.kernel.org/stable/c/43bc7d5707bbbf75e56db849b987193d6e866ec6)
- [https://git.kernel.org/stable/c/c5c95dbdc9011a56359df4dc00be829bbcc0b036](https://git.kernel.org/stable/c/c5c95dbdc9011a56359df4dc00be829bbcc0b036)

## Related threats

- [Linux kernel xen-netback double unmap memory corruption](https://junglewise.ai/threats/cve-2026-99287-in-the-linux-kernel-the-following-vulnerability-has-been-resolved)
- [Linux kernel x86 Hyper-V memory access violation](https://junglewise.ai/threats/cve-2026-99258-in-the-linux-kernel-the-following-vulnerability-has-been-resolved)
- [Linux kernel io_uring signal loss in worker exit](https://junglewise.ai/threats/cve-2026-99228-in-the-linux-kernel-the-following-vulnerability-has-been-resolved)
- [Linux kernel mv643xx_eth NULL pointer dereference in PHY probe](https://junglewise.ai/threats/cve-2026-99197-in-the-linux-kernel-the-following-vulnerability-has-been-resolved)
- [Linux kernel unicode map use-after-free in path lookup](https://junglewise.ai/threats/cve-2026-99180-in-the-linux-kernel-the-following-vulnerability-has-been-resolved)