CVE-2024-36029 json
mmc: sdhci-msm: pervent access to suspended controller
published 2024-05-30 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-35839
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
mmc: sdhci-msm: pervent access to suspended controller
Generic sdhci code registers LED device and uses host->runtime_suspended flag to protect access to it. The sdhci-msm driver doesn't set this flag, which causes a crash when LED is accessed while controller is runtime suspended. Fix this by setting the flag correctly.
Patch / fix
- Linux Linux 5.15.158, 6.1.90, 6.6.30, 6.8.9, 6.9
- linux Debian 12 6.1.90-1
- linux Debian 14, Debian 13 6.8.9-1
debian advisories DEBIAN-CVE-2024-36029
- linux Ubuntu 22.04 LTS 5.15.0-116.126
- linux Ubuntu 24.04 LTS 6.8.0-40.40
- linux-aws Ubuntu 22.04 LTS 5.15.0-1065.71
- linux-aws Ubuntu 24.04 LTS 6.8.0-1013.14
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1064.72
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1012.13
- linux-gke Ubuntu 22.04 LTS 5.15.0-1062.68
- linux-gke Ubuntu 24.04 LTS 6.8.0-1008.11
ubuntu advisories UBUNTU-CVE-2024-36029
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-25.1
- kernel-source-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-25.1
- kernel-livepatch-MICRO-6-0-RT_Update_5 Linux Micro 6.1, Linux Micro 6.0 1-1.1
- kernel-rt Linux Micro 6.0 6.4.0-9.1
- kernel-source-rt Linux Micro 6.0 6.4.0-9.1
- kernel-source Linux Micro 6.0 6.4.0-18.1
- kernel-default Linux Micro 6.0 6.4.0-18.1
- kernel-kvmsmall Linux Micro 6.0 6.4.0-18.1
suse advisories SUSE-SU-2025:20166-1SUSE-SU-2025:20249-1SUSE-SU-2025:20028-1SUSE-SU-2025:20008-1SUSE-SU-2024:2973-1SUSE-SU-2024:2203-1
- git.kernel.org/stable/c/1200481cd6069d16ce20133bcd86f5825e26a045 commit
- git.kernel.org/stable/c/a957ea5aa3d3518067a1ba32c6127322ad348d20 commit
- git.kernel.org/stable/c/56b99a52229d7f8cd1f53d899f57aa7eb4b199af commit
- git.kernel.org/stable/c/f653b04a818c490b045c97834d559911479aa1c5 commit
- git.kernel.org/stable/c/f8def10f73a516b771051a2f70f2f0446902cb4f commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2024-36029 updated cvss 4.4
kernel: mmc: sdhci-msm: pervent access to suspended controller
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/1200481cd6069d16ce20133bcd86f5825e26a045
patch
-
git.kernel.org
/stable/c/a957ea5aa3d3518067a1ba32c6127322ad348d20
patch
-
git.kernel.org
/stable/c/56b99a52229d7f8cd1f53d899f57aa7eb4b199af
patch
-
git.kernel.org
/stable/c/f653b04a818c490b045c97834d559911479aa1c5
patch
-
git.kernel.org
/stable/c/f8def10f73a516b771051a2f70f2f0446902cb4f
patch
Sources
- CVE List CVE-2024-36029
- NVD CVE-2024-36029
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.