CVE-2025-37870 (GCVE-0-2025-37870)
Vulnerability from cvelistv5
Published
2025-05-09 06:43
Modified
2025-09-03 13:06
Severity ?
VLAI Severity ?
EPSS score ?
Summary
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: prevent hang on link training fail
[Why]
When link training fails, the phy clock will be disabled. However, in
enable_streams, it is assumed that link training succeeded and the
mux selects the phy clock, causing a hang when a register write is made.
[How]
When enable_stream is hit, check if link training failed. If it did, fall
back to the ref clock to avoid a hang and keep the system in a recoverable
state.
References
Impacted products
{ "containers": { "cna": { "affected": [ { "defaultStatus": "unaffected", "product": "Linux", "programFiles": [ "drivers/gpu/drm/amd/display/dc/hwss/dcn20/dcn20_hwseq.c", "drivers/gpu/drm/amd/display/dc/hwss/dcn401/dcn401_hwseq.c" ], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [ { "lessThan": "0363c03672cd3191f037905bf981eb523a3b71b1", "status": "affected", "version": "7462475e3a06fbb0b36243b391296f9f411e9041", "versionType": "git" }, { "lessThan": "04bf4f2a497e9877c425c5124652e61fb8a1a0aa", "status": "affected", "version": "7462475e3a06fbb0b36243b391296f9f411e9041", "versionType": "git" }, { "lessThan": "8058061ed9d6bc259d1e678607b07d259342c08f", "status": "affected", "version": "7462475e3a06fbb0b36243b391296f9f411e9041", "versionType": "git" } ] }, { "defaultStatus": "affected", "product": "Linux", "programFiles": [ "drivers/gpu/drm/amd/display/dc/hwss/dcn20/dcn20_hwseq.c", "drivers/gpu/drm/amd/display/dc/hwss/dcn401/dcn401_hwseq.c" ], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [ { "status": "affected", "version": "6.3" }, { "lessThan": "6.3", "status": "unaffected", "version": "0", "versionType": "semver" }, { "lessThanOrEqual": "6.12.*", "status": "unaffected", "version": "6.12.25", "versionType": "semver" }, { "lessThanOrEqual": "6.14.*", "status": "unaffected", "version": "6.14.4", "versionType": "semver" }, { "lessThanOrEqual": "*", "status": "unaffected", "version": "6.15", "versionType": "original_commit_for_fix" } ] } ], "cpeApplicability": [ { "nodes": [ { "cpeMatch": [ { "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionEndExcluding": "6.12.25", "versionStartIncluding": "6.3", "vulnerable": true }, { "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionEndExcluding": "6.14.4", "versionStartIncluding": "6.3", "vulnerable": true }, { "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionEndExcluding": "6.15", "versionStartIncluding": "6.3", "vulnerable": true } ], "negate": false, "operator": "OR" } ] } ], "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: prevent hang on link training fail\n\n[Why]\nWhen link training fails, the phy clock will be disabled. However, in\nenable_streams, it is assumed that link training succeeded and the\nmux selects the phy clock, causing a hang when a register write is made.\n\n[How]\nWhen enable_stream is hit, check if link training failed. If it did, fall\nback to the ref clock to avoid a hang and keep the system in a recoverable\nstate." } ], "providerMetadata": { "dateUpdated": "2025-09-03T13:06:50.395Z", "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux" }, "references": [ { "url": "https://git.kernel.org/stable/c/0363c03672cd3191f037905bf981eb523a3b71b1" }, { "url": "https://git.kernel.org/stable/c/04bf4f2a497e9877c425c5124652e61fb8a1a0aa" }, { "url": "https://git.kernel.org/stable/c/8058061ed9d6bc259d1e678607b07d259342c08f" } ], "title": "drm/amd/display: prevent hang on link training fail", "x_generator": { "engine": "bippy-1.2.0" } } }, "cveMetadata": { "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "assignerShortName": "Linux", "cveId": "CVE-2025-37870", "datePublished": "2025-05-09T06:43:59.074Z", "dateReserved": "2025-04-16T04:51:23.959Z", "dateUpdated": "2025-09-03T13:06:50.395Z", "state": "PUBLISHED" }, "dataType": "CVE_RECORD", "dataVersion": "5.1", "vulnerability-lookup:meta": { "nvd": "{\"cve\":{\"id\":\"CVE-2025-37870\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-05-09T07:16:08.107\",\"lastModified\":\"2025-05-12T17:32:32.760\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\ndrm/amd/display: prevent hang on link training fail\\n\\n[Why]\\nWhen link training fails, the phy clock will be disabled. However, in\\nenable_streams, it is assumed that link training succeeded and the\\nmux selects the phy clock, causing a hang when a register write is made.\\n\\n[How]\\nWhen enable_stream is hit, check if link training failed. If it did, fall\\nback to the ref clock to avoid a hang and keep the system in a recoverable\\nstate.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: drm/amd/display: impide el bloqueo en caso de fallo del entrenamiento del enlace [Por qu\u00e9] Cuando el entrenamiento del enlace falla, el reloj f\u00edsico se desactiva. Sin embargo, en enable_streams, se asume que el entrenamiento del enlace se realiz\u00f3 correctamente y el multiplexor selecciona el reloj f\u00edsico, lo que provoca un bloqueo al escribir en un registro. [C\u00f3mo] Cuando se alcanza enable_stream, se comprueba si el entrenamiento del enlace ha fallado. En caso afirmativo, se recurre al reloj de referencia para evitar un bloqueo y mantener el sistema en un estado recuperable.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/0363c03672cd3191f037905bf981eb523a3b71b1\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/04bf4f2a497e9877c425c5124652e61fb8a1a0aa\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/8058061ed9d6bc259d1e678607b07d259342c08f\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}" } }
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…