CVE-2023-53225

spi: imx: Don't skip cleanup in remove's error path

MEDIUM

5.5

CVSS Score

Published: September 15, 2025 at 02:21 PM UTC

Updated: June 17, 2026 at 06:44 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: spi: imx: Don't skip cleanup in remove's error path Returning early in a platform driver's remove callback is wrong. In this case the dma resources are not released in the error path. this is never retried later and so this is a permanent leak. To fix this, only skip hardware disabling if waking the device fails.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

v ≥ 3.16.57v ≥ 3.18.94v ≥ 4.1.50v ≥ 4.14.17v ≥ 4.15.1v ≥ 4.4.115v ≥ 4.9.803.16.57 ≤ v < 3.173.18.94 ≤ v < 3.194.1.50 ≤ v < 4.24.14.17 ≤ v < 4.154.15.1 ≤ v < 4.164.15.1 ≤ v < 5.10.1804.16 ≤ v < 5.10.1804.16 ≤ v < 5.15.1114.16 ≤ v < 6.1.284.16 ≤ v < 6.2.154.16 ≤ v < 6.3.24.16 ≤ v < 6.44.4.115 ≤ v < 4.54.9.80 ≤ v < 4.105.11 ≤ v < 5.15.1115.16 ≤ v < 6.1.286.2 ≤ v < 6.2.156.3 ≤ v < 6.3.21333c3e996eb799286ee2ef2c01752da45bf926f28ae79a518421348abfc2a2dffd6a6b6e36994763.16.57 3.18.94 4.1.50 4.14.17 4.15.1 4.16 4.4.115 4.9.80b6aaaaed67b170a9841f0f598cd45ccbfe76e15ebac4bf53ca7c65d6c06808aab70c6caa0b9c78b9cfd96cbd607ab5d63a33cd63673221f4d572ea8cd593574aff0ab846136190b1729c151c736727ecf84a8d446a16379df5844bc2bd50f0b7431a4718fc58a98f1c98b22d31c53913cca38d5c43807cb4

Vendor states this is fixed in 11951c9e3f364d7ae3b568a0e52c8335d43066b5 (fixed)

Vendor states this is fixed in 57a463226638f1ceabbb029cbd21b0c94640f1b5 (fixed)

Vendor states this is fixed in 6d16305a1535873e0a8a8ae92ea2d9106ec2d7df (fixed)

Vendor states this is fixed in aa93a46f998a9069368026ac52bba96868c59157 (fixed)

Vendor states this is fixed in b64cb3f085fed296103c91f0db6acad30a021b36 (fixed)

Vendor states this is fixed in f90822ad63d11301e425311dac0c8e12ca1737b8 (fixed)

Affected range stops below 3.17, so it looks safe — our inference, not a vendor statement

Affected range stops below 3.19, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 4.16 (unaffected)

Affected range stops below 4.2, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.5, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 5.10.180 (unaffected)

Vendor states this is fixed in 5.15.111 (unaffected)

Vendor states this is fixed in 6.1.28 (unaffected)

Vendor states this is fixed in 6.2.15 (unaffected)

Vendor states this is fixed in 6.3.2 (unaffected)

Vendor states this is fixed in 6.4 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references