CVE-2022-48626

moxart: fix potential use-after-free on remove path

HIGH

7.8

CVSS Score

Published: February 25, 2024 at 02:03 PM UTC

Updated: June 17, 2026 at 05:15 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

HIGH7.8

Exploit prediction

EPSS 0.3%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: moxart: fix potential use-after-free on remove path It was reported that the mmc host structure could be accessed after it was freed in moxart_remove(), so fix this by saving the base register of the device and using it instead of the pointer dereference.

Affected

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

Linux Kernel · Linux

95%

3.16 ≤ v < 4.14.2663.16 ≤ v < 4.19.2293.16 ≤ v < 4.9.3013.16 ≤ v < 5.10.1003.16 ≤ v < 5.15.233.16 ≤ v < 5.16.93.16 ≤ v < 5.173.16 ≤ v < 5.4.1794.10 ≤ v < 4.14.2664.15 ≤ v < 4.19.2294.20 ≤ v < 5.4.1795.11 ≤ v < 5.15.235.16 ≤ v < 5.16.95.5 ≤ v < 5.10.1001b66e94e6b9995323190f31c51d8e1a6f516627e3.16

Vendor states this is fixed in 3a0a7ec5574b510b067cfc734b8bdb6564b31d4e (fixed)

Vendor states this is fixed in 7f901d53f120d1921f84f7b9b118e87e94b403c5 (fixed)

Vendor states this is fixed in 9c25d5ff1856b91bd4365e813f566cb59aaa9552 (fixed)

Vendor states this is fixed in af0e6c49438b1596e4be8a267d218a0c88a42323 (fixed)

Vendor states this is fixed in bd2db32e7c3e35bd4d9b8bbff689434a50893546 (fixed)

Vendor states this is fixed in be93028d306dac9f5b59ebebd9ec7abcfc69c156 (fixed)

Vendor states this is fixed in e6f580d0b3349646d4ee1ce0057eb273e8fb7e2e (fixed)

Vendor states this is fixed in f5dc193167591e88797262ec78515a0cbe79ff5f (fixed)

Vendor states this is fixed in 3.16 (unaffected)

Vendor states this is fixed in 4.14.266 (unaffected)

Vendor states this is fixed in 4.19.229 (unaffected)

Vendor states this is fixed in 4.9.301 (unaffected)