In the Linux kernel, the following vulnerability has been resolved:
tty: serial: imx: disable Ageing Timer interrupt request irq
There maybe pending USR interrupt before requesting irq, however
uart_add_one_port has not executed, so there will be kernel panic:
[ 0.795668] Unable to handle kernel NULL pointer dereference at virtual addre
ss 0000000000000080
[ 0.802701] Mem abort info:
[ 0.805367] ESR = 0x0000000096000004
[ 0.808950] EC = 0x25: DABT (current EL), IL = 32 bits
[ 0.814033] SET = 0, FnV = 0
[ 0.816950] EA = 0, S1PTW = 0
[ 0.819950] FSC = 0x04: level 0 translation fault
[ 0.824617] Data abort info:
[ 0.827367] ISV = 0, ISS = 0x00000004
[ 0.831033] CM = 0, WnR = 0
[ 0.833866] [0000000000000080] user address but active_mm is swapper
[ 0.839951] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP
[ 0.845953] Modules linked in:
[ 0.848869] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.1.1+g56321e101aca #1
[ 0.855617] Hardware name: Freescale i.MX8MP EVK (DT)
[ 0.860452] pstate: 000000c5 (nzcv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 0.867117] pc : __imx_uart_rxint.constprop.0+0x11c/0x2c0
[ 0.872283] lr : imx_uart_int+0xf8/0x1ec
The issue only happends in the inmate linux when Jailhouse hypervisor
enabled. The test procedure is:
while true; do
jailhouse enable imx8mp.cell
jailhouse cell linux xxxx
sleep 10
jailhouse cell destroy 1
jailhouse disable
sleep 5
done
And during the upper test, press keys to the 2nd linux console.
When `jailhouse cell destroy 1`, the 2nd linux has no chance to put
the uart to a quiese state, so USR1/2 may has pending interrupts. Then
when `jailhosue cell linux xx` to start 2nd linux again, the issue
trigger.
In order to disable irqs before requesting them, both UCR1 and UCR2 irqs
should be disabled, so here fix that, disable the Ageing Timer interrupt
in UCR2 as UCR1 does.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can crash an affected i.MX-based system during a narrow Jailhouse hypervisor workflow. A pending serial UART interrupt may fire before the UART port is fully registered, causing a kernel NULL pointer dereference and panic.
Executive priority
Treat this as a targeted availability risk for embedded or virtualized i.MX deployments, not a broad enterprise emergency. Patch affected operational technology, appliance, or lab systems where serial console restarts can disrupt service.
Technical view
The imx serial driver could leave the Ageing Timer interrupt enabled in UCR2 before requesting IRQs. In Jailhouse inmate Linux restart scenarios, pending USR interrupts may reach imx_uart_int before uart_add_one_port completes, triggering __imx_uart_rxint on incomplete state and panicking the kernel.
Likely exposure
Exposure appears limited to Linux kernels using the imx serial driver on i.MX platforms, especially Jailhouse inmate Linux environments. The bundle does not support broad exposure for typical Linux servers or unrelated hardware.
Exploitation context
The source describes reproduction through repeated Jailhouse enable, inmate Linux start, cell destroy, and console key input. KEV is false, and the bundle provides no evidence of active exploitation in the wild.
Researcher notes
The evidence is strong for root cause and fix direction, but incomplete for exact distribution package impact and CVSS severity. The affected version data in the bundle is sparse, so validate against vendor kernel trees and backports.
Mitigation direction
Apply vendor kernel updates containing the listed stable fixes.
Prioritize i.MX systems using Jailhouse inmate Linux and serial consoles.
Check distribution or board-vendor advisories for fixed kernel packages.
Avoid high-risk Jailhouse restart testing on production systems until patched.
Validation and detection
Inventory kernels on i.MX systems using the imx UART driver.
Check whether the kernel includes one of the referenced stable commits.
Review crash logs for NULL dereferences in imx_uart_int or __imx_uart_rxint.
Confirm Jailhouse inmate Linux systems no longer panic during restart testing.
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-54287 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
5Source 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 30, 2025, 12:23 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.