From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-36029: mmc: sdhci-msm: pervent access to suspended controller
Date: Thu, 30 May 2024 17:19:57 +0200 [thread overview]
Message-ID: <2024053057-CVE-2024-36029-e157@gregkh> (raw)
Description
===========
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.
The Linux kernel CVE team has assigned CVE-2024-36029 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.10 with commit 67e6db113c90 and fixed in 5.15.158 with commit 1200481cd606
Issue introduced in 4.10 with commit 67e6db113c90 and fixed in 6.1.90 with commit a957ea5aa3d3
Issue introduced in 4.10 with commit 67e6db113c90 and fixed in 6.6.30 with commit 56b99a52229d
Issue introduced in 4.10 with commit 67e6db113c90 and fixed in 6.8.9 with commit f653b04a818c
Issue introduced in 4.10 with commit 67e6db113c90 and fixed in 6.9 with commit f8def10f73a5
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2024-36029
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/mmc/host/sdhci-msm.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/1200481cd6069d16ce20133bcd86f5825e26a045
https://git.kernel.org/stable/c/a957ea5aa3d3518067a1ba32c6127322ad348d20
https://git.kernel.org/stable/c/56b99a52229d7f8cd1f53d899f57aa7eb4b199af
https://git.kernel.org/stable/c/f653b04a818c490b045c97834d559911479aa1c5
https://git.kernel.org/stable/c/f8def10f73a516b771051a2f70f2f0446902cb4f
reply other threads:[~2024-05-30 15:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2024053057-CVE-2024-36029-e157@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.