clk: spacemit: mark K1 pll1_d8 as critical
In the Linux kernel, the following vulnerability has been resolved: clk: spacemit: mark K1 pll1_d8 as critical The pll1_d8 clock is enabled by the boot loader, and is ultimately a parent for numerous clocks, including those used by APB and AXI buses. Guodong Xu discovered that this clock got disabled while responding to getting -EPROBE_DEFER when requesting a reset controller. The needed clock (CLK_DMA, along with its parents) had already been enabled. To respond to the probe deferral return, the CLK_DMA clock was disabled, and this led to parent clocks also reducing their enable count. When the enable count for pll1_d8 was decremented it became 0, which caused it to be disabled. This led to a system hang. Marking that clock critical resolves this by preventing it from being disabled. Define a new macro CCU_FACTOR_GATE_DEFINE() to allow clock flags to be supplied for a CCU_FACTOR_GATE clock.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.16.1
- CVEs
- CVE-2025-38633
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 6 Nov 2026, 02:58 UTC · Revision 1
Source evidence
clk: spacemit: mark K1 pll1_d8 as critical
core-osv · Original sourcePublished 22 Aug 2025, 16:00 UTC
In the Linux kernel, the following vulnerability has been resolved: clk: spacemit: mark K1 pll1_d8 as critical The pll1_d8 clock is enabled by the boot loader, and is ultimately a parent for numerous clocks, including those used by APB and AXI buses. Guodong Xu discovered that this clock got disabled while responding to getting -EPROBE_DEFER when requesting a reset controller. The needed clock (CLK_DMA, along with its parents) had already been enabled. To respond to the probe deferral return, the CLK_DMA clock was disabled, and this led to parent clocks also reducing their enable count. When the enable count for pll1_d8 was decremented it became 0, which caused it to be disabled. This led to a system hang. Marking that clock critical resolves this by preventing it from being disabled. Define a new macro CCU_FACTOR_GATE_DEFINE() to allow clock flags to be supplied for a CCU_FACTOR_GATE clock.
osv:CVE-2025-38633
Kernel
Fixed versions: 6.16.1
Complete source record
{
"id": "5f36c05d98dcf7b8ba12cff8a88b9aed8ac792fc57292a76f0d8389ede136dd3",
"url": "https://osv.dev/vulnerability/CVE-2025-38633",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "clk: spacemit: mark K1 pll1_d8 as critical",
"summary": "In the Linux kernel, the following vulnerability has been resolved: clk: spacemit: mark K1 pll1_d8 as critical The pll1_d8 clock is enabled by the boot loader, and is ultimately a parent for numerous clocks, including those used by APB and AXI buses. Guodong Xu discovered that this clock got disabled while responding to getting -EPROBE_DEFER when requesting a reset controller. The needed clock (CLK_DMA, along with its parents) had already been enabled. To respond to the probe deferral return, the CLK_DMA clock was disabled, and this led to parent clocks also reducing their enable count. When the enable count for pll1_d8 was decremented it became 0, which caused it to be disabled. This led to a system hang. Marking that clock critical resolves this by preventing it from being disabled. Define a new macro CCU_FACTOR_GATE_DEFINE() to allow clock flags to be supplied for a CCU_FACTOR_GATE clock.",
"evidence": "osv:CVE-2025-38633",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.16.1",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2025-38633",
"aliases": [
"CVE-2025-38633"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "1b72c59db0add8e47fa116b21f78ed0b09a264f3"
},
{
"fixed": "10948c00e548e9ad2ce9d765baf26dce2d9b806b"
},
{
"fixed": "7554729de27daf6d54bcf8689d863bbe267828bf"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38633.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.16.0"
},
{
"fixed": "6.16.1"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38633.json"
}
}
],
"modified": "2026-10-28T02:30:46.617115847Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/10948c00e548e9ad2ce9d765baf26dce2d9b806b",
"https://git.kernel.org/stable/c/7554729de27daf6d54bcf8689d863bbe267828bf",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38633.json",
"https://nvd.nist.gov/vuln/detail/CVE-2025-38633",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38633.json"
}
},
"related_cves": [
{
"value": "CVE-2025-38633",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 514456,
"published_at": "2025-08-22T16:00:41.434+00:00"
}