From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43313: ACPI: processor: Fix NULL-pointer dereference in acpi_processor_errata_piix4()
Date: Fri, 8 May 2026 15:12:18 +0200 [thread overview]
Message-ID: <2026050800-CVE-2026-43313-6ec3@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ACPI: processor: Fix NULL-pointer dereference in acpi_processor_errata_piix4()
In acpi_processor_errata_piix4(), the pointer dev is first assigned an IDE
device and then reassigned an ISA device:
dev = pci_get_subsys(..., PCI_DEVICE_ID_INTEL_82371AB, ...);
dev = pci_get_subsys(..., PCI_DEVICE_ID_INTEL_82371AB_0, ...);
If the first lookup succeeds but the second fails, dev becomes NULL. This
leads to a potential null-pointer dereference when dev_dbg() is called:
if (errata.piix4.bmisx)
dev_dbg(&dev->dev, ...);
To prevent this, use two temporary pointers and retrieve each device
independently, avoiding overwriting dev with a possible NULL value.
[ rjw: Subject adjustment, added an empty code line ]
The Linux kernel CVE team has assigned CVE-2026-43313 to this issue.
Affected and fixed versions
===========================
Fixed in 5.15.202 with commit 06724a60cfa9767ea90b0f5d3dfb5cdd251b64f5
Fixed in 6.1.165 with commit ad86ac604f8391c0212a91412d4f764c7a85f254
Fixed in 6.6.128 with commit 01e8751b37a366b1ca561add0042f2ceb18c03bf
Fixed in 6.12.75 with commit b803811485ac0b2f774b6bf3abc8b999ba3b7033
Fixed in 6.18.16 with commit 29f60d3d06818d40118a30d663231f027ae87a05
Fixed in 6.19.6 with commit 0398b641be2b66c2fc7e0163c606ef19372e7ad5
Fixed in 7.0 with commit f132e089fe89cadc2098991f0a3cb05c3f824ac6
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-43313
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/acpi/acpi_processor.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/06724a60cfa9767ea90b0f5d3dfb5cdd251b64f5
https://git.kernel.org/stable/c/ad86ac604f8391c0212a91412d4f764c7a85f254
https://git.kernel.org/stable/c/01e8751b37a366b1ca561add0042f2ceb18c03bf
https://git.kernel.org/stable/c/b803811485ac0b2f774b6bf3abc8b999ba3b7033
https://git.kernel.org/stable/c/29f60d3d06818d40118a30d663231f027ae87a05
https://git.kernel.org/stable/c/0398b641be2b66c2fc7e0163c606ef19372e7ad5
https://git.kernel.org/stable/c/f132e089fe89cadc2098991f0a3cb05c3f824ac6
reply other threads:[~2026-05-08 13:14 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=2026050800-CVE-2026-43313-6ec3@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