---
title: "CVE-2026-89777: Linux Kernel vfio/pci - Use After Free"
description: "Linux kernel vfio/pci contains a use-after-free vulnerability caused by a dangling pointer in vdev->msi_perm after init failure, letting attackers cause kernel crashes or execute arbitrary code, exploit requires device open failure condition."
url: https://panop.io/threat-heartbeat/CVE-2026-89777/
---

# CVE-2026-89777 Linux Kernel vfio/pci - Use After Free

Linux kernel vfio/pci contains a use-after-free vulnerability caused by a dangling pointer in vdev->msi\_perm after init failure, letting attackers cause kernel crashes or execute arbitrary code, exploit requires device open failure condition.

CVSS base score 8.8 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Required

EPSS

0.16% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-89777)

## Details

Type

Use After Free

Impact

Denial Of Service, Privilege Escalation

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Published

16 September 2026

Updated

15 October 2026

## Vendor fix

Update to the latest Linux kernel version containing the fix that nulls vdev->msi\_perm after free.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-89777](https://nvd.nist.gov/vuln/detail/CVE-2026-89777)
- [https://git.kernel.org/stable/c/f0eea8f9013676b42289ec35941e848b8a543e19](https://git.kernel.org/stable/c/f0eea8f9013676b42289ec35941e848b8a543e19)
- [https://git.kernel.org/stable/c/fda8fb7e8179561693a786a7af593f6b944a21c1](https://git.kernel.org/stable/c/fda8fb7e8179561693a786a7af593f6b944a21c1)
- [https://git.kernel.org/stable/c/25cdd2a492d868cff1e519a60fe282909c52d385](https://git.kernel.org/stable/c/25cdd2a492d868cff1e519a60fe282909c52d385)
- [https://git.kernel.org/stable/c/533d0c5feef85ee6404b9f41d5564fac6971a008](https://git.kernel.org/stable/c/533d0c5feef85ee6404b9f41d5564fac6971a008)
- [https://git.kernel.org/stable/c/812f1db7f0755a19ef16ecdc5cec51bcabc5eda5](https://git.kernel.org/stable/c/812f1db7f0755a19ef16ecdc5cec51bcabc5eda5)
- [https://git.kernel.org/stable/c/d665a1688af7f8fefd7c0eb04f2a37122ce007f4](https://git.kernel.org/stable/c/d665a1688af7f8fefd7c0eb04f2a37122ce007f4)
- [https://git.kernel.org/stable/c/dc77acfeb979dded39b247b60fef0399536bfa77](https://git.kernel.org/stable/c/dc77acfeb979dded39b247b60fef0399536bfa77)
- [https://git.kernel.org/stable/c/eb84cd81040e58dd05ac190f561f2115e3367249](https://git.kernel.org/stable/c/eb84cd81040e58dd05ac190f561f2115e3367249)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)