# CVE-2026-92522: ACPI: processor: validate MADT IOAPIC entry bounds

> An attacker with local access can trigger memory corruption in the Linux kernel via malformed ACPI MADT IOAPIC entries, potentially leading to code execution or system crash.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-101924, BELL-CVE-2026-92522, DEBIAN-CVE-2026-92522, GHSA-jg3q-2vpp-2763, UBUNTU-CVE-2026-92522

## What is CVE-2026-92522?

CVE-2026-92522 is a high-severity memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-92522?


## How do I fix CVE-2026-92522?

Apply the vendor's patch.

## Is CVE-2026-92522 being exploited?

There is no known exploitation of CVE-2026-92522 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92522 and fix it if it is affected.

What it is: CVE-2026-92522 is a high-severity memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92522 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92522/ (Markdown: https://insights.sbomify.com/CVE-2026-92522/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92522
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92522
- OSV: https://osv.dev/vulnerability/CVE-2026-92522

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92522/
Summaries are generated and may contain mistakes; the official description above is the record.