Answer in brief
CVE-2023-53388 records a Unknown severity vulnerability in drm/mediatek: Clean dangling pointer on bind error path. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2023-53388 records a Unknown severity vulnerability in drm/mediatek: Clean dangling pointer on bind error path. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=119f5173628aa7a0c3cf9db83460d40709e8241d <9a48f99aa7bea15e0b1d8b0040c46b4792eddf3b || >=119f5173628aa7a0c3cf9db83460d40709e8241d <a161f1d92aabb3b8463f752bdc3474dc3a5ec0e5 || >=119f5173628aa7a0c3cf9db83460d40709e8241d <6a89ddee1686a8872384aaa9f0bcfa6b675acd86 || >=119f5173628aa7a0c3cf9db83460d40709e8241d <49cf87919daeeeeeb9e924c39bdd9203af434461 || >=119f5173628aa7a0c3cf9db83460d40709e8241d <7b551a501fa714890e55bae73efede1185728d72 || >=119f5173628aa7a0c3cf9db83460d40709e8241d <f3887c771576c5d740c5c5b8bf654a8ab8020b7d || >=119f5173628aa7a0c3cf9db83460d40709e8241d <36aa8c61af55675ed967900fbe5deb32d776f051 | 9a48f99aa7bea15e0b1d8b0040c46b4792eddf3b, a161f1d92aabb3b8463f752bdc3474dc3a5ec0e5, 6a89ddee1686a8872384aaa9f0bcfa6b675acd86, 49cf87919daeeeeeb9e924c39bdd9203af434461, 7b551a501fa714890e55bae73efede1185728d72, f3887c771576c5d740c5c5b8bf654a8ab8020b7d, 36aa8c61af55675ed967900fbe5deb32d776f051 |
| Linux/Linuxgeneric | 4.7 | Not reported |
Published upstream
Sep 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Clean dangling pointer on bind error path mtk_drm_bind() can fail, in which case drm_dev_put() is called, destroying the drm_device object. However a pointer to it was still being held in the private object, and that pointer would be passed along to DRM in mtk_drm_sys_prepare() if a suspend were triggered at that point, resulting in a panic. Clean the pointer when destroying the object in the error path to prevent this from happening.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=119f5173628aa7a0c3cf9db83460d40709e8241d <9a48f99aa7bea15e0b1d8b0040c46b4792eddf3b || >=119f5173628aa7a0c3cf9db83460d40709e8241d <a161f1d92aabb3b8463f752bdc3474dc3a5ec0e5 || >=119f5173628aa7a0c3cf9db83460d40709e8241d <6a89ddee1686a8872384aaa9f0bcfa6b675acd86 || >=119f5173628aa7a0c3cf9db83460d40709e8241d <49cf87919daeeeeeb9e924c39bdd9203af434461 || >=119f5173628aa7a0c3cf9db83460d40709e8241d <7b551a501fa714890e55bae73efede1185728d72 || >=119f5173628aa7a0c3cf9db83460d40709e8241d <f3887c771576c5d740c5c5b8bf654a8ab8020b7d || >=119f5173628aa7a0c3cf9db83460d40709e8241d <36aa8c61af55675ed967900fbe5deb32d776f051 | 9a48f99aa7bea15e0b1d8b0040c46b4792eddf3b, a161f1d92aabb3b8463f752bdc3474dc3a5ec0e5, 6a89ddee1686a8872384aaa9f0bcfa6b675acd86, 49cf87919daeeeeeb9e924c39bdd9203af434461, 7b551a501fa714890e55bae73efede1185728d72, f3887c771576c5d740c5c5b8bf654a8ab8020b7d, 36aa8c61af55675ed967900fbe5deb32d776f051 |
| Linux/Linuxgeneric | 4.7 | Not reported |
Published upstream
Sep 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Clean dangling pointer on bind error path mtk_drm_bind() can fail, in which case drm_dev_put() is called, destroying the drm_device object. However a pointer to it was still being held in the private object, and that pointer would be passed along to DRM in mtk_drm_sys_prepare() if a suspend were triggered at that point, resulting in a panic. Clean the pointer when destroying the object in the error path to prevent this from happening.
Quoted source text, attributed separately from HOL analysis.