CVE-2024-53056: drm/mediatek: Fix potential NULL dereference in mtk_crtc_destroy()
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 32ac6dccf561af97f20a3831430577d8a978e672, 4018651ba5c409034149f297d3dd3328b91561fd, 5.16.
Low priority for now. Upgrade to Linux Linux 32ac6dccf561af97f20a3831430577d8a978e672, 4018651ba5c409034149f297d3dd3328b91561fd, 5.16 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Fix potential NULL dereference in mtk_crtc_destroy() In mtk_crtc_create(), if the call to mbox_request_channel() fails then we set the "mtk_crtc->cmdq_client.chan" pointer to NULL. In that situation, we do not call cmdq_pkt_create(). During the cleanup, we need to check if the "mtk_crtc->cmdq_client.chan" is NULL first before calling cmdq_pkt_destroy(). Calling cmdq_pkt_destroy() is unnecessary if we didn't call cmdq_pkt_create() and it will result in a NULL pointer dereference.
- Published
- Nov 19, 2024
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- CWE-476
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 5.5
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2c4396693698e876e559768d3d3a150c672ec384, 5.17affected
- 7627122fd1c06800a1fe624e9fb3c269796115e8 and later · before 32ac6dccf561af97f20a3831430577d8a978e672affected · git
- 7627122fd1c06800a1fe624e9fb3c269796115e8 and later · before fb05e973698f4af008c7fb6e0cfa6a2fa1d98409affected · git
- 7627122fd1c06800a1fe624e9fb3c269796115e8 and later · before c60583a87cb4a85b69d1f448f0be5eb6ec62cbb2affected · git
- 7627122fd1c06800a1fe624e9fb3c269796115e8 and later · before 4018651ba5c409034149f297d3dd3328b91561fdaffected · git
- 5.15.54 and later · before 5.16affected · semver
- before 5.17not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.158 and later · up to and including 6.6.*not affected · semver
- 6.11.7 and later · up to and including 6.11.*not affected · semver
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.17 and later · before 6.11.7
- linux linux kernel6.12
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.192-1 | 6.1.192-1 |
| Debian:13 | linux | before 6.11.7-1 | 6.11.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-53042Nov 19, 2024 · ipv4: ip_tunnel: Fix suspicious RCU usage warning in ip_tunnel_init_flow()22Monitor
- ← EarlierCVE-2024-53051Nov 19, 2024 · drm/i915/hdcp: Add encoder check in intel_hdcp_get_capability22Monitor
- Later →CVE-2024-53057Nov 19, 2024 · net/sched: stop qdisc_tree_reduce_backlog on TC_H_ROOT31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 32ac6dccf561af97f20a3831430577d8a978e672 | Vendor (CNA) |
| Linux Linux | 4018651ba5c409034149f297d3dd3328b91561fd | Vendor (CNA) |
| Linux Linux | 5.16 | Vendor (CNA) |
| Linux Linux | c60583a87cb4a85b69d1f448f0be5eb6ec62cbb2 | Vendor (CNA) |
| Linux Linux | fb05e973698f4af008c7fb6e0cfa6a2fa1d98409 | Vendor (CNA) |
| debian:linux | 6.1.192-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.11.7-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.