From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43487: ata: libata-core: Disable LPM on ST1000DM010-2EP102
Date: Wed, 13 May 2026 17:08:55 +0200 [thread overview]
Message-ID: <2026051350-CVE-2026-43487-9a69@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ata: libata-core: Disable LPM on ST1000DM010-2EP102
According to a user report, the ST1000DM010-2EP102 has problems with LPM,
causing random system freezes. The drive belongs to the same BarraCuda
family as the ST2000DM008-2FR102 which has the same issue.
The Linux kernel CVE team has assigned CVE-2026-43487 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.9 with commit 7627a0edef548c4c4dea62df51cc26bfe5bbcab8 and fixed in 6.12.78 with commit f897b72cc74d24e7106716184f450d4045a6289b
Issue introduced in 6.9 with commit 7627a0edef548c4c4dea62df51cc26bfe5bbcab8 and fixed in 6.18.19 with commit 87f0349beaacab2ac60c4a1b6dcff254cef7d5a0
Issue introduced in 6.9 with commit 7627a0edef548c4c4dea62df51cc26bfe5bbcab8 and fixed in 6.19.9 with commit a4bfb1947eda615fe0b2fc54beb6bedc03372e34
Issue introduced in 6.9 with commit 7627a0edef548c4c4dea62df51cc26bfe5bbcab8 and fixed in 7.0 with commit b3b1d3ae1d87bc9398fb715c945968bf4c75a09a
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-2026-43487
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/ata/libata-core.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/f897b72cc74d24e7106716184f450d4045a6289b
https://git.kernel.org/stable/c/87f0349beaacab2ac60c4a1b6dcff254cef7d5a0
https://git.kernel.org/stable/c/a4bfb1947eda615fe0b2fc54beb6bedc03372e34
https://git.kernel.org/stable/c/b3b1d3ae1d87bc9398fb715c945968bf4c75a09a
reply other threads:[~2026-05-13 15:08 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=2026051350-CVE-2026-43487-9a69@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox