CVE-2023-54059: soc: mediatek: mtk-svs: Enable the IRQ later
In the Linux kernel, the following vulnerability has been resolved:
soc: mediatek: mtk-svs: Enable the IRQ later
If the system does not come from reset (like when is booted via
kexec()), the peripheral might triger an IRQ before the data structures
are initialised.
[ 0.227710] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000f08
[ 0.227913] Call trace:
[ 0.227918] svs_isr+0x8c/0x538
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel bug in the MediaTek SVS driver. On certain boot paths, especially kexec where hardware is not fully reset, an interrupt can fire before the driver is ready, causing a NULL pointer dereference and likely a kernel crash.
Executive priority
Treat as a targeted reliability issue, not a broad internet-facing emergency. Prioritize embedded, appliance, or fleet systems using MediaTek Linux kernels where failed boots create outage risk.
Technical view
The mtk-svs driver enabled IRQ handling before required data structures were initialized. If the peripheral generated an interrupt early, svs_isr could dereference NULL during boot. The kernel stable references resolve this by enabling the IRQ later.
Likely exposure
Exposure appears limited to Linux systems using affected MediaTek SoC SVS support, particularly systems that boot through kexec or otherwise do not start from full hardware reset.
Exploitation context
The provided sources do not show active exploitation, public exploit code, KEV listing, remote reachability, or privilege escalation. Evidence points to a boot-time availability failure under specific hardware and boot conditions.
Researcher notes
The source data lacks CVSS, CWE, exploitability detail, and precise fixed release mapping beyond stable commit references. Analysis should stay scoped to the IRQ initialization ordering flaw and observed svs_isr NULL dereference.
Mitigation direction
Apply vendor or distribution kernel updates containing the referenced stable fixes.
If patching is delayed, avoid kexec or non-reset boot paths where operationally possible.
Check device vendor advisories for backported fixes and supported kernel versions.
Prioritize systems where boot reliability or unattended recovery is business critical.
Validation and detection
Inventory Linux devices using MediaTek SoCs and the mtk-svs driver.
Confirm kernel versions against vendor advisories or the referenced stable commits.
Review boot logs for NULL pointer dereferences involving svs_isr.
Test kexec boot behavior in a lab after applying updates.
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-54059 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
4Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Dec 24, 2025, 12:23 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.