Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Buy Us a Coffee

CVE-2023-53389— drm/mediatek: dp: Only trigger DRM HPD events if bridge is attached

EPSS 0.02% · P5
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2023-53389

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
drm/mediatek: dp: Only trigger DRM HPD events if bridge is attached
Source: NVD (National Vulnerability Database)
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: dp: Only trigger DRM HPD events if bridge is attached The MediaTek DisplayPort interface bridge driver starts its interrupts as soon as its probed. However when the interrupts trigger the bridge might not have been attached to a DRM device. As drm_helper_hpd_irq_event() does not check whether the passed in drm_device is valid or not, a NULL pointer passed in results in a kernel NULL pointer dereference in it. Check whether the bridge is attached and only trigger an HPD event if it is.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于未检查桥接器是否附加，可能导致空指针取消引用。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux f70ac097a2cf5d4b67b2c1bbb73196c573ffcb7b ~ 6524d3d58797975cc40b85be1e9b89721b4e8d0b -
LinuxLinux 6.1 -

II. Public POCs for CVE-2023-53389

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2023-53389

请登录查看更多情报信息。

Same Patch Batch · Linux · 2025-09-18 · 121 CVEs total

CVE-2022-50405net/tunnel: wait until all sk_user_data reader finish before releasing the sock
CVE-2022-50418wifi: ath11k: mhi: fix potential memory leak in ath11k_mhi_register()
CVE-2022-50417drm/panfrost: Fix GEM handle creation ref-counting
CVE-2022-50416irqchip/wpcm450: Fix memory leak in wpcm450_aic_of_init()
CVE-2022-50415parisc: led: Fix potential null-ptr-deref in start_task()
CVE-2022-50414scsi: fcoe: Fix transport not deattached when fcoe_if_init() fails
CVE-2022-50413wifi: mac80211: fix use-after-free
CVE-2022-50412drm: bridge: adv7511: unregister cec i2c device after cec adapter
CVE-2022-50411ACPICA: Fix error code path in acpi_ds_call_control_method()
CVE-2022-50410NFSD: Protect against send buffer overflow in NFSv2 READ
CVE-2022-50409net: If sock is dead don't access sock's sk_wq in sk_stream_wait_memory
CVE-2022-50407crypto: hisilicon/qm - increase the memory of local variables
CVE-2022-50408wifi: brcmfmac: fix use-after-free bug in brcmf_netdev_start_xmit()
CVE-2022-50406iomap: iomap: fix memory corruption when recording errors during writeback
CVE-2022-50404fbdev: fbcon: release buffer when fbcon_do_set_font() failed
CVE-2023-53410USB: ULPI: fix memory leak with using debugfs_lookup()
CVE-2023-53413USB: isp116x: fix memory leak with using debugfs_lookup()
CVE-2023-53412USB: gadget: bcm63xx_udc: fix memory leak with using debugfs_lookup()
CVE-2023-53411PM: EM: fix memory leak with using debugfs_lookup()
CVE-2023-53408trace/blktrace: fix memory leak with using debugfs_lookup()

Showing top 20 of 121 CVEs. View all on vendor page → →

IV. Related Vulnerabilities

Same product: Linux
Same vendor: Linux

V. Comments for CVE-2023-53389

No comments yet

Leave a comment