LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53812: media: mediatek: vcodec: fix decoder disable pm crash

In the Linux kernel, the following vulnerability has been resolved: media: mediatek: vcodec: fix decoder disable pm crash Can't call pm_runtime_disable when the architecture support sub device for 'dev->pm.dev' is NUll, or will get below crash log. [ 10.771551] pc : _raw_spin_lock_irq+0x4c/0xa0 [ 10.771556] lr : __pm_runtime_disable+0x30/0x130 [ 10.771558] sp : ffffffc01e4cb800 [ 10.771559] x29: ffffffc01e4cb800 x28: ffffffdf082108a8 [ 10.771563] x27: ffffffc01e4cbd70 x26: ffffff8605df55f0 [ 10.771567] x25: 0000000000000002 x24: 0000000000000002 [ 10.771570] x23: ffffff85c0dc9c00 x22: 0000000000000001 [ 10.771573] x21: 0000000000000001 x20: 0000000000000000 [ 10.771577] x19: 00000000000000f4 x18: ffffffdf2e9fbe18 [ 10.771580] x17: 0000000000000000 x16: ffffffdf2df13c74 [ 10.771583] x15: 00000000000002ea x14: 0000000000000058 [ 10.771587] x13: ffffffdf2de1b62c x12: ffffffdf2e9e30e4 [ 10.771590] x11: 0000000000000000 x10: 0000000000000001 [ 10.771593] x9 : 0000000000000000 x8 : 00000000000000f4 [ 10.771596] x7 : 6bff6264632c6264 x6 : 0000000000008000 [ 10.771600] x5 : 0080000000000000 x4 : 0000000000000001 [ 10.771603] x3 : 0000000000000008 x2 : 0000000000000001 [ 10.771608] x1 : 0000000000000000 x0 : 00000000000000f4 [ 10.771613] Call trace: [ 10.771617] _raw_spin_lock_irq+0x4c/0xa0 [ 10.771620] __pm_runtime_disable+0x30/0x130 [ 10.771657] mtk_vcodec_probe+0x69c/0x728 [mtk_vcodec_dec 800cc929d6631f79f9b273254c8db94d0d3500dc] [ 10.771662] platform_drv_probe+0x9c/0xbc [ 10.771665] really_probe+0x13c/0x3a0 [ 10.771668] driver_probe_device+0x84/0xc0 [ 10.771671] device_driver_attach+0x54/0x78

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel crash bug in the MediaTek video decoder driver. On affected systems, the driver can call runtime power-management disable logic when an internal device pointer is null, causing a kernel crash during device probing. Exposure appears limited to Linux devices using the MediaTek vcodec decoder path.

Executive priority

Address through normal kernel maintenance unless affected MediaTek devices are crashing or business-critical. There is no source-supported evidence of active exploitation, but unpatched embedded or appliance fleets could face reliability impact.

Technical view

The flaw is in media/mediatek/vcodec decoder initialization. The source describes mtk_vcodec_probe reaching __pm_runtime_disable with dev->pm.dev null, leading to a crash in _raw_spin_lock_irq. Stable kernel commits are listed as the resolution sources. No CVSS, CWE, or detailed exploitability data is provided.

Likely exposure

Likely limited to Linux systems with MediaTek SoCs or hardware using the mtk_vcodec_dec driver, especially kernels in the affected version data. Generic servers without MediaTek video decoder hardware are unlikely to be exposed based on the source bundle.

Exploitation context

The bundle does not show active exploitation, and KEV is false. The evidence describes a crash path during driver probe, not a remote attack path. Treat this primarily as an availability and device-stability issue unless vendor guidance says otherwise.

Researcher notes

Source evidence is narrow: a null dev->pm.dev condition in MediaTek vcodec decoder probe and stable commit references. The bundle lacks CVSS, CWE, exploit prerequisites, attacker model, and distribution-specific fixed versions, so conclusions should remain conservative.

Mitigation direction

  • Apply a vendor kernel update containing the referenced stable fixes.
  • Prioritize MediaTek-based devices using the mtk_vcodec_dec driver.
  • Check distribution advisories for backported fixes before relying on version numbers alone.
  • If no patch exists, follow vendor guidance for operational workarounds.

Validation and detection

  • Inventory kernels on MediaTek-based devices and appliances.
  • Check kernel package changelogs for the referenced stable commit IDs.
  • Review boot logs for mtk_vcodec_probe or __pm_runtime_disable crash traces.
  • After updating, confirm the MediaTek decoder driver probes without crashing.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-53812 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxba31a5b39400a7b500b3f022a351218b179038dc, ba31a5b39400a7b500b3f022a351218b179038dc, ba31a5b39400a7b500b3f022a351218b179038dc, ba31a5b39400a7b500b3f022a351218b179038dcunaffected
LinuxLinux5.18, 0, 6.1.28, 6.2.15, 6.3.2, 6.4affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.