CVE-2025-38583: clk: xilinx: vcu: unregister pll_post only if registered correctly
Published Aug 19, 2025
·Updated
clk: xilinx: vcu: unregister pllpost only if registered correctly
Affected Software
11 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=5.12<5.15.190
Linux Linux kernel>=5.16<6.1.148
Linux Linux kernel>=6.2<6.6.102
Linux Linux kernel>=6.7<6.12.42
Linux Linux kernel>=6.13<6.15.10
Linux Linux kernel>=6.16<6.16.1
Debian Debian Linux=11.0
Microsoft cbl2 kernel 5.15.186.1-1
Microsoft azl3 kernel 6.6.96.2-2
Microsoft azl3 kernel 6.6.96.2-1
Remediation
Event History
Aug 19, 2025
CVE Published
via MITRE·05:03 PM
Data Sourced
via MITRE·05:03 PM
Description
Data Sourced
via NVD·05:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Sep 4, 2025
Data Sourced
via Microsoft·04:35 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·11:35 AM
SeverityAffected Software
Updated
via Microsoft·11:35 AM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2025-38583?
CVE-2025-38583 is considered to have a significant impact due to potential kernel failures.
2
How do I fix CVE-2025-38583?
To fix CVE-2025-38583, ensure you update the Linux kernel to a patched version from your distribution.
3
What systems are affected by CVE-2025-38583?
CVE-2025-38583 affects the Linux Kernel, particularly systems using the Xilinx VCU clock driver.
4
What are the potential consequences of CVE-2025-38583?
Exploitation of CVE-2025-38583 could lead to kernel crashes or unexpected behavior in affected systems.
5
Is CVE-2025-38583 related to any specific functionality in the Linux kernel?
Yes, CVE-2025-38583 is specifically related to the registration and unregistration process of the pll_post in the Linux clock framework.