LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49506: drm/mediatek: Add vblank register/unregister callback functions

In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Add vblank register/unregister callback functions We encountered a kernel panic issue that callback data will be NULL when it's using in ovl irq handler. There is a timing issue between mtk_disp_ovl_irq_handler() and mtk_ovl_disable_vblank(). To resolve this issue, we use the flow to register/unregister vblank cb: - Register callback function and callback data when crtc creates. - Unregister callback function and callback data when crtc destroies. With this solution, we can assure callback data will not be NULL when vblank is disable.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can cause a kernel panic in MediaTek graphics/display handling. In business terms, affected devices could unexpectedly crash rather than suffer confirmed data theft. The public record does not provide a CVSS score or evidence of active exploitation.

Executive priority

Handle through normal kernel patch management unless affected MediaTek-based devices are operationally critical. Escalate for fleets where a kernel panic could disrupt kiosks, appliances, mobile devices, or embedded services.

Technical view

The flaw is a timing issue between mtk_disp_ovl_irq_handler() and mtk_ovl_disable_vblank(). Callback data may be NULL when used in the overlay interrupt handler. The kernel fix changes vblank callback registration to occur when the CRTC is created and unregistration when it is destroyed.

Likely exposure

Exposure appears limited to Linux systems using the MediaTek DRM display driver path. This is most relevant to embedded, mobile, or ARM-based devices with MediaTek display hardware. Generic servers without this driver path are unlikely to be affected, but distro backports may change version conclusions.

Exploitation context

The provided sources describe a kernel panic condition, not privilege escalation or remote code execution. CISA KEV is false in the bundle, and no cited source states active exploitation. Exploitability details are incomplete from the provided evidence.

Researcher notes

The source evidence identifies a NULL callback-data panic caused by a race in vblank disable handling. The record lacks CVSS, CWE, detailed affected ranges, and exploitation evidence. Validate against actual kernel configuration, driver use, and downstream vendor backports.

Mitigation direction

  • Apply Linux kernel or vendor updates that include the referenced stable fixes.
  • Check Linux distribution advisories for backported MediaTek DRM fixes.
  • Prioritize affected MediaTek-based devices that require high display availability.
  • Monitor vendor guidance because no standalone mitigation is named in the sources.

Validation and detection

  • Inventory Linux devices using MediaTek DRM display hardware or drivers.
  • Compare running kernel packages against vendor fixed advisories and referenced stable commits.
  • Review crash history for kernel panics involving MediaTek overlay or vblank handling.
  • Confirm compensating controls only as operational risk reduction, not a vulnerability fix.
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-2022-49506 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
LinuxLinux9b0704988b151824a51133dc4c921f4273c5d839, 9b0704988b151824a51133dc4c921f4273c5d839, 9b0704988b151824a51133dc4c921f4273c5d839, 9b0704988b151824a51133dc4c921f4273c5d839unaffected
LinuxLinux5.12, 0, 5.15.54, 5.17.14, 5.18.3, 5.19affected
Weakness

CWE details

No CWE listed

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