CVE-2026-53237·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: gpio: mvebu: fix NULL pointer dereference in suspend/resume mvebu_pwm_suspend() and mvebu_pwm_resume() are called for all GPIO banks during suspend/resume, but not all banks have PWM functionality. GPIO banks without PWM have mvchip->mvpwm set to NULL. Calling mvebu_pwm_suspend() with mvpwm == NULL causes a NULL pointer dereference when it tries to access mvpwm->blink_select. Unable to handle kernel NULL pointer dereference at virtual address 00000020 when write [00000020] *pgd=00000000 Internal error: Oops: 815 [#1] PREEMPT ARM Modules linked in: CPU: 0 UID: 0 PID: 406 Comm: sh Not tainted 6.12.74-rt12-yocto-standard-g4e96f98fb7db-dirty #353 Hardware name: Marvell Armada 370/XP (Device Tree) PC is at regmap_mmio_read+0x38/0x54 LR is at regmap_mmio_read+0x38/0x54 pc : [<c05fd2ac>] lr : [<c05fd2ac>] psr: 200f0013 sp : f0c11d10 ip : 00000000 fp : c100d2f0 r10: c14fb854 r9 : 00000000 r8 : 00000000 r7 : c1799c00 r6 : 00000020 r5 : 00000020 r4 : c179c7c0 r3 : f0a231a0 r2 : 00000020 r1 : 00000020 r0 : 00000000 Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment none Control: 10c5387d Table: 135ec059 DAC: 00000051 Call trace: regmap_mmio_read from _regmap_bus_reg_read+0x78/0xac _regmap_bus_reg_read from _regmap_read+0x60/0x154 _regmap_read from regmap_read+0x3c/0x60 regmap_read from mvebu_gpio_suspend+0xa4/0x14c mvebu_gpio_suspend from dpm_run_callback+0x54/0x180 dpm_run_callback from device_suspend+0x124/0x630 device_suspend from dpm_suspend+0x124/0x270 dpm_suspend from dpm_suspend_start+0x64/0x6c dpm_suspend_start from suspend_devices_and_enter+0x140/0x8e8 suspend_devices_and_enter from pm_suspend+0x2fc/0x308 pm_suspend from state_store+0x6c/0xc8 state_store from kernfs_fop_write_iter+0x10c/0x1f8 kernfs_fop_write_iter from vfs_write+0x270/0x468 vfs_write from ksys_write+0x70/0xf0 ksys_write from ret_fast_syscall+0x0/0x54 Add a NULL check for mvchip->mvpwm before calling the PWM suspend/resume functions.
- Severity
- medium
- Software
- Kernel
- Fixed in
- 7.0.13
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.12% — higher than 2% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Affected versions
From: 6.19
Until: 7.0.13
Fixed in: 7.0.13
How to fix this CVE
Update your Linux kernel to version 7.0.13 or later to resolve this NULL pointer dereference in the mvebu GPIO driver. The vulnerability affects GPIO banks without PWM functionality during system suspend/resume cycles. Apply the patch immediately if you are running kernel versions 6.19 through 7.0.12, particularly on ARM-based systems using Marvell Armada 370/XP hardware.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Check current kernel version: uname -r — verify it is 7.0.13 or later
- Confirm vulnerable kernel range: if uname output shows 6.19.x through 7.0.12, the system is vulnerable
- Identify affected hardware: check for Marvell Armada devices in dmesg | grep -i marvell or cat /proc/cpuinfo | grep -i marvell
- Review suspend/resume logs: journalctl -b -0 | grep -i 'NULL pointer dereference\|gpio\|suspend' to check for exploitation attempts
- Verify patch applied: grep -r 'mvchip->mvpwm' /boot/config-$(uname -r) or check kernel build logs for NULL check presence
FAQ
What is CVE-2026-53237?
This vulnerability is a NULL pointer dereference in the Linux kernel's mvebu GPIO driver that occurs when the suspend/resume functions attempt to access PWM registers on GPIO banks that lack PWM functionality, causing a kernel panic during system suspend cycles on Marvell Armada hardware.
Is CVE-2026-53237 being actively exploited?
No, this vulnerability is not listed on the CISA KEV catalog and no public exploits are currently available. However, it can be triggered locally by any user with permission to initiate system suspend operations.
What versions of Kernel are affected by CVE-2026-53237?
Linux kernel versions 6.19 through 7.0.12 are vulnerable. The vulnerability has been patched in version 7.0.13 and later stable releases.
How do I check if my server is vulnerable to CVE-2026-53237?
Run 'uname -r' and compare the output against the vulnerable range (6.19.x to 7.0.12). If your kernel version falls within this range and your hardware includes Marvell Armada chipsets, your system is vulnerable.
Does Defensia detect CVE-2026-53237?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2026-53237 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/3cb53f89049c3769e102ac5b7692e679a1d45510
- https://git.kernel.org/stable/c/4ef24338eda3c7e96d6f94a988266ff16ed3985d
- https://git.kernel.org/stable/c/6136c1474db88272231573e222896e1998d34662
- https://git.kernel.org/stable/c/7db09011ce62162d72897fc4856b4425245dfe35
- https://git.kernel.org/stable/c/b9ad50d7505ebd48282ec3630258dc820fc85c81
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-53237. Free for 1 server.
Get started free