{"metadata": {"vulnerability": "CVE-2026-99450", "count": 11, "kinds": {"milestone": 4, "sighting": 1, "kev": 0, "other": 6}, "linked_omitted": 0}, "data": [{"timestamp": "2026-09-25T10:25:14.416Z", "date_only": false, "value": "2026-09-25T10:25:14.416Z", "kind": "milestone", "label": "Reserved", "source": "cvelistv5", "record": "CVE-2026-99450", "field": "cveMetadata.dateReserved"}, {"timestamp": "2026-11-19T14:41:46.677Z", "date_only": false, "value": "2026-11-19T14:41:46.677Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99450", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2026-11-19T14:41:46.677Z", "date_only": false, "value": "2026-11-19T14:41:46.677Z", "kind": "other", "label": "Updated", "source": "cvelistv5", "record": "CVE-2026-99450", "field": "cveMetadata.dateUpdated"}, {"timestamp": "2026-11-19T14:41:46.677Z", "date_only": false, "value": "2026-11-19T14:41:46.677Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / Linux", "record": "CVE-2026-99450", "field": "containers.cna.providerMetadata.dateUpdated"}, {"timestamp": "2026-11-19T15:17:58Z", "date_only": false, "value": "2026-11-19T15:17:58Z", "kind": "other", "label": "Nvd published at", "source": "github \u00b7 GHSA-H637-GMPM-JHQ7", "record": "GHSA-H637-GMPM-JHQ7", "field": "database_specific.nvd_published_at", "linked_record": true}, {"timestamp": "2026-11-19T15:17:58.833Z", "date_only": false, "value": "2026-11-19T15:17:58.833", "kind": "milestone", "label": "Published", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99450", "record": "FKIE_CVE-2026-99450", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-11-19T15:17:58.833Z", "date_only": false, "value": "2026-11-19T15:17:58.833", "kind": "other", "label": "Updated", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99450", "record": "FKIE_CVE-2026-99450", "field": "lastModified", "linked_record": true}, {"timestamp": "2026-11-19T15:31:24Z", "date_only": false, "value": "2026-11-19T15:31:24Z", "kind": "milestone", "label": "Published", "source": "github \u00b7 GHSA-H637-GMPM-JHQ7", "record": "GHSA-H637-GMPM-JHQ7", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-11-19T15:31:24Z", "date_only": false, "value": "2026-11-19T15:31:24Z", "kind": "other", "label": "Updated", "source": "github \u00b7 GHSA-H637-GMPM-JHQ7", "record": "GHSA-H637-GMPM-JHQ7", "field": "modified", "linked_record": true}, {"timestamp": "2026-11-19T16:20:49.562Z", "date_only": false, "value": "2026-11-19T16:20:49.562385Z", "kind": "sighting", "label": "Seen", "source": "https://infosec.exchange/users/cve/statuses/117644017602656519", "record": "CVE-2026-99450", "field": "creation_timestamp", "uuid": "f89fb2e8-b8eb-4d2e-9bba-e7c2c7eaf156", "content": "CVE-2026-99450 vfio/nvgrace-gpu: Use a core-only open_device in fallback mode In the Linux kernel, the following vulnerability has been resolved:\nvfio/nvgrace-gpu: Use a core-only open_device in fallback mode\nWhen the ACPI memory properties are missing or the C2C link is down, thedevice is exposed through nvgrace_gpu_pci_core_ops.  That table opensthrough nvgrace_gpu_open_device() but closes throughvfio_pci_core_close_device(), so open and close are not symmetric.\nnvgrace_gpu_open_device() registers nvdev-&gt;usemem for poison handlingunconditionally.  In fallback mode usemem.memlength is zero, andregister_pfn_address_space() inserts a node covering [0, ULONG_MAX].Nothing removes it: a second open fails with -EBUSY, and once the deviceis unbound the node outlives the nvdev that contains it.  The next openafter a rebind reports:\n  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:   &lt;TASK&gt;   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   &lt;/TASK&gt;\n  Allocated by task 188:   ...   _vfio_alloc_device+0x3a/0x500   nvgrace_gpu_probe+0xcb/0x660   local_pci_probe+0xcf/0x170   ...\n  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   ...\nGive the fallback table its own open_device that only callsvfio_pci_core_enable() and vfio_pci_core_finish_enable(), thecounterpart of vfio_pci_core_close_device().  Fallback mode then nevertouches the nvgrace memory regions, as Alex suggested.\nThis should be safe because the fallback table uses the vfio-pci coreread, write and mmap handlers, so nothing there uses the statenvgrace_gpu_open_device() sets up.  The one visible difference is that afallback open no longer fails when BAR0 cannot be mapped, which matchesvfio-pci.\nhttps://www.cve.org/CVERecord?id=CVE-2026-99450https://git.kernel.org/stable/c/a2942b3abb5bddd1bac418abd61fb5f0616ab897https://git.kernel.org/stable/c/9c48b994b66d7b585698f9aaee8ff559a7755c0a#kernel #Linux#CVE_2026_99450#bot", "url": "https://infosec.exchange/users/cve/statuses/117644017602656519"}, {"timestamp": "2026-11-19T19:09:23.206Z", "date_only": false, "value": "2026-11-19T19:09:23.206732+00:00", "kind": "other", "label": "Updated", "source": "debian_tracker \u00b7 DEBIAN-CVE-2026-99450", "record": "DEBIAN-CVE-2026-99450", "field": "modified", "linked_record": true}], "metrics": {"as_of": "2026-11-20T04:37:10.395Z", "anchors": {"origin": {"timestamp": "2026-11-19T14:41:46.677Z", "date_only": false, "value": "2026-11-19T14:41:46.677Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99450", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "discovery": null, "report": null, "acknowledgement": null, "disclosure": {"timestamp": "2026-11-19T14:41:46.677Z", "date_only": false, "value": "2026-11-19T14:41:46.677Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99450", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "exploit_publication": null, "exploitation": null, "patch": null}, "vendor_response_time": {"available": false, "missing": ["start", "end"]}, "time_to_exploit": {"available": false, "missing": ["end"]}, "disclosure_to_exploit": {"available": false, "missing": ["end"]}, "disclosure_to_exploit_publication": {"available": false, "missing": ["end"]}, "time_to_patch": {"available": false, "missing": ["start", "end"]}, "total_time_to_patch": {"available": false, "missing": ["start", "end"]}, "disclosure_to_patch": {"available": false, "missing": ["end"]}, "time_unpatched": {"available": true, "seconds": 50123.718604, "hours": 13.923255167777778, "days": 0.5801356319907408, "min_seconds": 50123.718604, "max_seconds": 50123.718604, "approximate": false, "ongoing": true, "order_known": true, "batch_listing": false, "end_before_start": false, "start": {"timestamp": "2026-11-19T14:41:46.677Z", "date_only": false, "value": "2026-11-19T14:41:46.677Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99450", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "end": {"timestamp": "2026-11-20T04:37:10.395Z", "date_only": false, "label": "As of", "source": "Calculation clock"}}, "exploitation_to_patch": {"available": false, "missing": ["start"]}, "exploit_publication_to_patch": {"available": false, "missing": ["start"]}}}
