From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89444: platform/x86: dell-wmi-sysman: Don't hex dump attribute security buffer
Date: Fri, 11 Sep 2026 21:42:13 +0200 [thread overview]
Message-ID: <2026091157-CVE-2026-89444-b0f4@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
platform/x86: dell-wmi-sysman: Don't hex dump attribute security buffer
set_attribute() populates the security area of the BIOS attribute request
buffer with the current admin password via populate_security_buffer(), then
dumps the whole request buffer with print_hex_dump_bytes(). This can expose
the plaintext admin password in the kernel log.
The same issue was fixed for the password attribute path by
commit d1a196e0a6dc ("platform/x86: dell-wmi-sysman: Don't hex dump
plaintext password data"). Remove the remaining dump from the BIOS
attribute path.
The Linux kernel CVE team has assigned CVE-2026-89444 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.11 with commit e8a60aa7404bfef37705da5607c97737073ac38d and fixed in 6.12.109 with commit ceeee18c927958b74a04b92cf084fc496fa21e8b
Issue introduced in 5.11 with commit e8a60aa7404bfef37705da5607c97737073ac38d and fixed in 6.18.50 with commit 22222f92b0a5116eb4aac4be81e7b770adfa32ee
Issue introduced in 5.11 with commit e8a60aa7404bfef37705da5607c97737073ac38d and fixed in 7.2.4 with commit eb73b9d51490bec4f73ac6efdba5ac535fcfee74
Issue introduced in 5.11 with commit e8a60aa7404bfef37705da5607c97737073ac38d and fixed in 7.3-rc1 with commit 83c80495e45eddf64c6525fb582d8db68f256b71
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-89444
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/platform/x86/dell/dell-wmi-sysman/biosattr-interface.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/ceeee18c927958b74a04b92cf084fc496fa21e8b
https://git.kernel.org/stable/c/22222f92b0a5116eb4aac4be81e7b770adfa32ee
https://git.kernel.org/stable/c/eb73b9d51490bec4f73ac6efdba5ac535fcfee74
https://git.kernel.org/stable/c/83c80495e45eddf64c6525fb582d8db68f256b71
reply other threads:[~2026-09-11 19:52 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=2026091157-CVE-2026-89444-b0f4@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 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.