From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-92522: ACPI: processor: validate MADT IOAPIC entry bounds
Date: Thu, 17 Sep 2026 17:15:12 +0100 [thread overview]
Message-ID: <2026091731-CVE-2026-92522-effb@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ACPI: processor: validate MADT IOAPIC entry bounds
The IOAPIC hotplug lookup parses both MADT and _MAT records directly.
The MADT walk previously used a subtable's declared length to advance
the cursor after only locating a generic header. The _MAT path likewise
passed a generic header to the IOAPIC helper.
Validate that a current record has a complete generic header, that its
declared length is contained in the available record range, and that a
typed IOAPIC record contains the full fixed IOAPIC body before reading
its fields. Use the same relation for both MADT and _MAT provider
paths.
The Linux kernel CVE team has assigned CVE-2026-92522 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.0 with commit ecf5636dcd59cd5508641f995cc4c2bafedbb995 and fixed in 5.10.270 with commit 5601bd81bc290a724ed47797d22c16cba4d7ed9f
Issue introduced in 4.0 with commit ecf5636dcd59cd5508641f995cc4c2bafedbb995 and fixed in 5.15.221 with commit ff82e3374e9103d046b2a82f4315d9a422ff097d
Issue introduced in 4.0 with commit ecf5636dcd59cd5508641f995cc4c2bafedbb995 and fixed in 6.1.188 with commit 2a5520065e76000f8c979d3d7b3d861ccaaecf1e
Issue introduced in 4.0 with commit ecf5636dcd59cd5508641f995cc4c2bafedbb995 and fixed in 6.6.157 with commit 8e67b58c04990817ac2dbf8ae03353be6a358cd4
Issue introduced in 4.0 with commit ecf5636dcd59cd5508641f995cc4c2bafedbb995 and fixed in 6.12.110 with commit 74d84320f8e37955eb286a7777843d554e6e75b2
Issue introduced in 4.0 with commit ecf5636dcd59cd5508641f995cc4c2bafedbb995 and fixed in 6.18.52 with commit 4d8ecaa332c163f2b44aa5027bf061950b71b5f3
Issue introduced in 4.0 with commit ecf5636dcd59cd5508641f995cc4c2bafedbb995 and fixed in 7.2.6 with commit 355bee5f11acb116cd256588631b4028ca562646
Issue introduced in 4.0 with commit ecf5636dcd59cd5508641f995cc4c2bafedbb995 and fixed in 7.3-rc1 with commit 2c50ffdc73f3a70d745d249f509fc290754121e6
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-92522
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/processor_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/5601bd81bc290a724ed47797d22c16cba4d7ed9f
https://git.kernel.org/stable/c/ff82e3374e9103d046b2a82f4315d9a422ff097d
https://git.kernel.org/stable/c/2a5520065e76000f8c979d3d7b3d861ccaaecf1e
https://git.kernel.org/stable/c/8e67b58c04990817ac2dbf8ae03353be6a358cd4
https://git.kernel.org/stable/c/74d84320f8e37955eb286a7777843d554e6e75b2
https://git.kernel.org/stable/c/4d8ecaa332c163f2b44aa5027bf061950b71b5f3
https://git.kernel.org/stable/c/355bee5f11acb116cd256588631b4028ca562646
https://git.kernel.org/stable/c/2c50ffdc73f3a70d745d249f509fc290754121e6
reply other threads:[~2026-09-17 16:35 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=2026091731-CVE-2026-92522-effb@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.