{"metadata": {"vulnerability": "CVE-2026-99485", "count": 11, "kinds": {"milestone": 4, "sighting": 1, "kev": 0, "other": 6}, "linked_omitted": 0}, "data": [{"timestamp": "2026-09-25T10:25:14.418Z", "date_only": false, "value": "2026-09-25T10:25:14.418Z", "kind": "milestone", "label": "Reserved", "source": "cvelistv5", "record": "CVE-2026-99485", "field": "cveMetadata.dateReserved"}, {"timestamp": "2026-11-19T14:43:23.095Z", "date_only": false, "value": "2026-11-19T14:43:23.095Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99485", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2026-11-19T14:43:23.095Z", "date_only": false, "value": "2026-11-19T14:43:23.095Z", "kind": "other", "label": "Updated", "source": "cvelistv5", "record": "CVE-2026-99485", "field": "cveMetadata.dateUpdated"}, {"timestamp": "2026-11-19T14:43:23.095Z", "date_only": false, "value": "2026-11-19T14:43:23.095Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / Linux", "record": "CVE-2026-99485", "field": "containers.cna.providerMetadata.dateUpdated"}, {"timestamp": "2026-11-19T15:18:03Z", "date_only": false, "value": "2026-11-19T15:18:03Z", "kind": "other", "label": "Nvd published at", "source": "github \u00b7 GHSA-2255-VXMV-HCQM", "record": "GHSA-2255-VXMV-HCQM", "field": "database_specific.nvd_published_at", "linked_record": true}, {"timestamp": "2026-11-19T15:18:03.267Z", "date_only": false, "value": "2026-11-19T15:18:03.267", "kind": "milestone", "label": "Published", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99485", "record": "FKIE_CVE-2026-99485", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-11-19T15:18:03.267Z", "date_only": false, "value": "2026-11-19T15:18:03.267", "kind": "other", "label": "Updated", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99485", "record": "FKIE_CVE-2026-99485", "field": "lastModified", "linked_record": true}, {"timestamp": "2026-11-19T15:31:26Z", "date_only": false, "value": "2026-11-19T15:31:26Z", "kind": "milestone", "label": "Published", "source": "github \u00b7 GHSA-2255-VXMV-HCQM", "record": "GHSA-2255-VXMV-HCQM", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-11-19T15:31:26Z", "date_only": false, "value": "2026-11-19T15:31:26Z", "kind": "other", "label": "Updated", "source": "github \u00b7 GHSA-2255-VXMV-HCQM", "record": "GHSA-2255-VXMV-HCQM", "field": "modified", "linked_record": true}, {"timestamp": "2026-11-19T16:44:27.610Z", "date_only": false, "value": "2026-11-19T16:44:27.610530Z", "kind": "sighting", "label": "Seen", "source": "https://infosec.exchange/users/cve/statuses/117644110529327221", "record": "CVE-2026-99485", "field": "creation_timestamp", "uuid": "5113608e-688a-43a5-99eb-c51db0d9ec65", "content": "CVE-2026-99485 accel/amdxdna: clear the mailbox channel pointer when starting it fails In the Linux kernel, the following vulnerability has been resolved:\naccel/amdxdna: clear the mailbox channel pointer when starting it fails\naie2_create_context() allocates a mailbox channel, starts it, and on afailed start frees it again:\n\thwctx-&gt;priv-&gt;mbox_chann = xdna_mailbox_alloc_channel(ndev-&gt;mbox);\t...\tret = xdna_mailbox_start_channel(hwctx-&gt;priv-&gt;mbox_chann, ...);\tif (ret)\t\tgoto free_channel;\t...free_channel:\txdna_mailbox_free_channel(hwctx-&gt;priv-&gt;mbox_chann);\nhwctx-&gt;priv-&gt;mbox_chann keeps pointing at the freed channel. Thatpointer is the driver's own test for whether a hardware context has ausable channel: aie2_destroy_context() returns early on NULL,aie2_sched_job_run() refuses to run a job on NULL, and the messagehelpers return -ENODEV on NULL. A stale pointer passes all of them.\nIt matters on the restart path. aie2_hwctx_restart() callsaie2_create_context() again on a hardware context that is already live,after aie2_hwctx_stop() has torn its channel down, and the contextsurvives a failure there: aie2_sched_job_timedout() discards the returnvalue entirely, and aie2_hwctx_resume() only propagates it. What isleft is a live hardware context holding a freed channel, and everylater user of it takes the non-NULL branch:\n  - the next job submitted reaches xdna_mailbox_send_msg() on the freed    channel, via the !mbox_chann guard in aie2_sched_job_run(),  - a second command timeout reaches aie2_hwctx_stop() -&gt;    aie2_destroy_context(),  - closing the device reaches aie2_hwctx_fini() -&gt;    aie2_release_resource() -&gt; xrs_release_resource() -&gt;    aie2_xrs_unload() -&gt; aie2_destroy_context(),\nand aie2_destroy_context() then calls xdna_mailbox_stop_channel()followed by xdna_mailbox_free_channel() on memory that was alreadyfreed: a use-after-free, and a second free of the same channel.\nThe AIE4 management channel already does this correctly -aie4_mailbox_start() clears ndev-&gt;aie.mgmt_chann right after freeingit. Do the same here.\nThe create path itself is not affected: when aie2_xrs_load() fails,xrs_allocate_resource() removes the solver node without calling-&gt;unload, and aie2_hwctx_init() frees hwctx-&gt;priv, so the stale pointernever outlives the structure holding it.\nStarting a channel can fail today without this patch: the ring buffersizes firmware reports are rejected unless both are powers of two, andrequest_irq() can fail.\nhttps://www.cve.org/CVERecord?id=CVE-2026-99485https://git.kernel.org/stable/c/35003a3a2221207ded92ca4c60a54c2f83136473https://git.kernel.org/stable/c/2117e3d96a4fd1ee13fa28b31494ff5f5db6ccf4#kernel #Linux#CVE_2026_99485#bot", "url": "https://infosec.exchange/users/cve/statuses/117644110529327221"}, {"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-99485", "record": "DEBIAN-CVE-2026-99485", "field": "modified", "linked_record": true}], "metrics": {"as_of": "2026-11-20T04:29:39.520Z", "anchors": {"origin": {"timestamp": "2026-11-19T14:43:23.095Z", "date_only": false, "value": "2026-11-19T14:43:23.095Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99485", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "discovery": null, "report": null, "acknowledgement": null, "disclosure": {"timestamp": "2026-11-19T14:43:23.095Z", "date_only": false, "value": "2026-11-19T14:43:23.095Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99485", "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": 49576.425305, "hours": 13.771229251388888, "days": 0.5738012188078704, "min_seconds": 49576.425305, "max_seconds": 49576.425305, "approximate": false, "ongoing": true, "order_known": true, "batch_listing": false, "end_before_start": false, "start": {"timestamp": "2026-11-19T14:43:23.095Z", "date_only": false, "value": "2026-11-19T14:43:23.095Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99485", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "end": {"timestamp": "2026-11-20T04:29:39.520Z", "date_only": false, "label": "As of", "source": "Calculation clock"}}, "exploitation_to_patch": {"available": false, "missing": ["start"]}, "exploit_publication_to_patch": {"available": false, "missing": ["start"]}}}
