# CVE-2026-64511: ACPI: NFIT: core: Fix possible NULL pointer dereference

> A NULL pointer dereference in the Linux kernel ACPI NFIT driver allows local attackers to cause a system crash via specific firmware notifications.

- **Severity:** Not scored
- **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:** 25 Jul 2026
- **Updated:** 17 Aug 2026
- **Also known as:** AZL-93885, BELL-CVE-2026-64511, DEBIAN-CVE-2026-64511, GHSA-fx53-fh8q-8mmr, ROOT-OS-UBUNTU-2204-CVE-2026-64511, UBUNTU-CVE-2026-64511

## What is CVE-2026-64511?

CVE-2026-64511 is a vulnerability in Linux, published on 25 Jul 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: NFIT: core: Fix possible NULL pointer dereference

After commit 9b311b7313d6 ("ACPI: NFIT: Install Notify() handler before
getting NFIT table"), acpi_nfit_probe() installs an ACPI notify handler
for the NFIT device before checking the presence of the NFIT table.  If
that table is not there, 0 is returned without allocating the acpi_desc
object and setting the driver data pointer of the NFIT device.  If the
platform firmware triggers an NFIT_NOTIFY_UC_MEMORY_ERROR notification
on the NFIT device at that point, acpi_nfit_uc_error_notify() will
dereference a NULL pointer.

Prevent that from occurring by adding an acpi_desc check against NULL
to acpi_nfit_uc_error_notify().

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


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

Apply the vendor's patch.

## Is CVE-2026-64511 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-64511 is a vulnerability in Linux, published on 25 Jul 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-64511 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-64511/ (Markdown: https://insights.sbomify.com/CVE-2026-64511/index.md)
```

## Sources

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

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