LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50625: serial: amba-pl011: avoid SBSA UART accessing DMACR register

In the Linux kernel, the following vulnerability has been resolved: serial: amba-pl011: avoid SBSA UART accessing DMACR register Chapter "B Generic UART" in "ARM Server Base System Architecture" [1] documentation describes a generic UART interface. Such generic UART does not support DMA. In current code, sbsa_uart_pops and amba_pl011_pops share the same stop_rx operation, which will invoke pl011_dma_rx_stop, leading to an access of the DMACR register. This commit adds a using_rx_dma check in pl011_dma_rx_stop to avoid the access to DMACR register for SBSA UARTs which does not support DMA. When the kernel enables DMA engine with "CONFIG_DMA_ENGINE=y", Linux SBSA PL011 driver will access PL011 DMACR register in some functions. For most real SBSA Pl011 hardware implementations, the DMACR write behaviour will be ignored. So these DMACR operations will not cause obvious problems. But for some virtual SBSA PL011 hardware, like Xen virtual SBSA PL011 (vpl011) device, the behaviour might be different. Xen vpl011 emulation will inject a data abort to guest, when guest is accessing an unimplemented UART register. As Xen VPL011 is SBSA compatible, it will not implement DMACR register. So when Linux SBSA PL011 driver access DMACR register, it will get an unhandled data abort fault and the application will get a segmentation fault: Unhandled fault at 0xffffffc00944d048 Mem abort info: ESR = 0x96000000 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x00: ttbr address size fault Data abort info: ISV = 0, ISS = 0x00000000 CM = 0, WnR = 0 swapper pgtable: 4k pages, 39-bit VAs, pgdp=0000000020e2e000 [ffffffc00944d048] pgd=100000003ffff803, p4d=100000003ffff803, pud=100000003ffff803, pmd=100000003fffa803, pte=006800009c090f13 Internal error: ttbr address size fault: 96000000 [#1] PREEMPT SMP ... Call trace: pl011_stop_rx+0x70/0x80 tty_port_shutdown+0x7c/0xb4 tty_port_close+0x60/0xcc uart_close+0x34/0x8c tty_release+0x144/0x4c0 __fput+0x78/0x220 ____fput+0x1c/0x30 task_work_run+0x88/0xc0 do_notify_resume+0x8d0/0x123c el0_svc+0xa8/0xc0 el0t_64_sync_handler+0xa4/0x130 el0t_64_sync+0x1a0/0x1a4 Code: b9000083 b901f001 794038a0 8b000042 (b9000041) ---[ end trace 83dd93df15c3216f ]--- note: bootlogd[132] exited with preempt_count 1 /etc/rcS.d/S07bootlogd: line 47: 132 Segmentation fault start-stop-daemon This has been discussed in the Xen community, and we think it should fix this in Linux. See [2] for more information. [1] https://developer.arm.com/documentation/den0094/c/?lang=en [2] https://lists.xenproject.org/archives/html/xen-devel/2022-11/msg00543.html

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel driver flaw affecting SBSA PL011 UART handling, mainly relevant to ARM server or virtualized environments. The driver may touch a DMA register that SBSA UARTs do not implement. On Xen virtual SBSA PL011 devices, that can trigger a guest fault and process crash. No active exploitation is reported in the provided sources.

Executive priority

Treat as targeted infrastructure maintenance, not an emergency internet-wide threat. Prioritize affected ARM virtualization platforms because the issue can destabilize guests or services relying on serial console behavior. Track through normal kernel patch cycles unless critical Xen ARM workloads are exposed.

Technical view

The Linux amba-pl011 serial driver shared stop_rx behavior between standard PL011 and SBSA UART paths. With CONFIG_DMA_ENGINE=y, pl011_dma_rx_stop could access DMACR even though SBSA UART has no DMA support. Xen VPL011 may inject a data abort on that unimplemented register access. The referenced kernel fixes add a using_rx_dma check before accessing DMACR.

Likely exposure

Exposure appears limited to Linux systems using SBSA PL011 UARTs, especially Xen virtual SBSA PL011 on ARM, with DMA engine enabled. Conventional SBSA PL011 hardware may ignore the write and show no obvious issue, according to the source description.

Exploitation context

The provided sources describe a reliability failure, not a remote compromise path. The observed impact is a guest data abort and application segmentation fault during UART shutdown paths. CISA KEV is false in the bundle, and no cited source states active exploitation.

Researcher notes

CVSS, CWE, and detailed exploitability data are not provided in the bundle. The clearest affected scenario is Xen VPL011, where unimplemented DMACR access causes a guest fault. Avoid assuming broader impact beyond SBSA PL011 configurations without vendor confirmation.

Mitigation direction

  • Review vendor kernel advisories for CVE-2022-50625 and applicable stable backports.
  • Update to a kernel containing the referenced amba-pl011 SBSA UART fix.
  • Prioritize Xen ARM guests using virtual SBSA PL011 devices.
  • If unable to patch, ask the OS vendor for supported workarounds.

Validation and detection

  • Inventory ARM Linux systems and Xen guests using SBSA PL011 or VPL011 UARTs.
  • Check whether kernels are built with CONFIG_DMA_ENGINE enabled.
  • Compare running kernel source or package changelog against referenced stable commits.
  • Review logs for data aborts involving pl011_stop_rx or tty shutdown paths.
Prepared
Confidence
medium
Sources
6

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-50625 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
0Timeline events
0ADP providers
10Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0dd1e247fd39aed20fd2baacc62ca44d82534798, 0dd1e247fd39aed20fd2baacc62ca44d82534798, 0dd1e247fd39aed20fd2baacc62ca44d82534798, 0dd1e247fd39aed20fd2baacc62ca44d82534798, 0dd1e247fd39aed20fd2baacc62ca44d82534798, 0dd1e247fd39aed20fd2baacc62ca44d82534798, 0dd1e247fd39aed20fd2baacc62ca44d82534798, 0dd1e247fd39aed20fd2baacc62ca44d82534798, 0dd1e247fd39aed20fd2baacc62ca44d82534798unaffected
LinuxLinux4.2, 0, 4.9.337, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2, 6.2affected
Weakness

CWE details

No CWE listed

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