nday
CVE-2026-99450

vfio/nvgrace-gpu: Use a core-only open_device in fallback mode

Linux / Linux

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

tags productLinux kernel product typeoperating system
why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

Linux kernel
affected products in the CVE record: Linux · Linux
operating system
affected products in the CVE record: Linux · Linuxthe product type of Linux kernel in nday's product registry
stage
DIS
disclosed
cvss
no score yet

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
11-19T14:41Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

In the Linux kernel, the following vulnerability has been resolved:

vfio/nvgrace-gpu: Use a core-only open_device in fallback mode

When the ACPI memory properties are missing or the C2C link is down, the device is exposed through nvgrace_gpu_pci_core_ops. That table opens through nvgrace_gpu_open_device() but closes through vfio_pci_core_close_device(), so open and close are not symmetric.

nvgrace_gpu_open_device() registers nvdev->usemem for poison handling unconditionally. In fallback mode usemem.memlength is zero, and register_pfn_address_space() inserts a node covering [0, ULONG_MAX]. Nothing removes it: a second open fails with -EBUSY, and once the device is unbound the node outlives the nvdev that contains it. The next open after a rebind reports:

BUG: KASAN: slab-use-after-free in interval_tree_iter_first+0x209/0x310
Read of size 8 at addr ffff88800894aa30 by task nvgrace_repro/203
Call Trace:
 <TASK>
 dump_stack_lvl+0x5d/0x80
 print_report+0x153/0x4c6
 kasan_report+0xe4/0x1a0
 interval_tree_iter_first+0x209/0x310
 register_pfn_address_space+0x97/0x100
 nvgrace_gpu_open_device+0x21c/0x730
 vfio_df_open+0x213/0x520
 vfio_df_ioctl_bind_iommufd+0x3e8/0x6e0
 vfio_device_fops_unl_ioctl+0x782/0x1570
 __x64_sys_ioctl+0x13c/0x1c0
 do_syscall_64+0x106/0x630
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
 </TASK>

Allocated by task 188:
 ...
 _vfio_alloc_device+0x3a/0x500
 nvgrace_gpu_probe+0xcb/0x660
 local_pci_probe+0xcf/0x170
 ...

Freed by task 188:
 ...
 kfree+0x20d/0x600
 device_release+0xcf/0x250
 kobject_put+0x152/0x2f0
 pci_device_remove+0xb0/0x1c0
 device_release_driver_internal+0x38d/0x540
 unbind_store+0xde/0x100
 ...

Give the fallback table its own open_device that only calls vfio_pci_core_enable() and vfio_pci_core_finish_enable(), the counterpart of vfio_pci_core_close_device(). Fallback mode then never touches the nvgrace memory regions, as Alex suggested.

This should be safe because the fallback table uses the vfio-pci core read, write and mmap handlers, so nothing there uses the state nvgrace_gpu_open_device() sets up. The one visible difference is that a fallback open no longer fails when BAR0 cannot be mapped, which matches vfio-pci.

Original text of the CVE record (cvelist), shown as published.

Event log

+DISdisclosed

CVE record published by Linux.

src cvelist · nday , observed live · raw
{
  "id": 484766,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-99450",
  "occurred_at": "2026-11-19T14:41:46.677Z",
  "observed_at": "2026-11-19T15:00:30.436713Z",
  "is_backfill": false,
  "dedupe_key": "",
  "detail": {
    "state": "PUBLISHED",
    "date_published": "2026-11-19T14:41:46.677Z",
    "assigner_short_name": "Linux"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.