CVE-2021-47108
- Source
- https://cve.org/CVERecord?id=CVE-2021-47108
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2021-47108.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2021-47108
- Downstream
- Related
- Published
- 2024-03-04T19:15:18Z
- Modified
- 2026-03-14T11:18:57Z
- Severity
-
- 5.5 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
- Summary
- [none]
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
drm/mediatek: hdmi: Perform NULL pointer check for mtk_hdmi_conf
In commit 41ca9caaae0b ("drm/mediatek: hdmi: Add check for CEA modes only") a check for CEA modes was added to function mtk_hdmi_bridge_mode_valid() in order to address possible issues on MT8167; moreover, with commit c91026a938c2 ("drm/mediatek: hdmi: Add optional limit on maximal HDMI mode clock") another similar check was introduced.
Unfortunately though, at the time of writing, MT8173 does not provide any mtk_hdmi_conf structure and this is crashing the kernel with NULL pointer upon entering mtk_hdmi_bridge_mode_valid(), which happens as soon as a HDMI cable gets plugged in.
To fix this regression, add a NULL pointer check for hdmi->conf in the said function, restoring HDMI functionality and avoiding NULL pointer kernel panics.
- References
Affected packages
Git /
Database specific
source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2021-47108.json"
unresolved_ranges
[
{
"events": [
{
"introduced": "5.14"
},
{
"fixed": "5.15.12"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "5.16-rc1"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "5.16-rc2"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "5.16-rc3"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "5.16-rc4"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "5.16-rc5"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "5.16-rc6"
}
]
}
]