{"metadata": {"vulnerability": "CVE-2026-79976", "count": 10, "kinds": {"milestone": 3, "sighting": 1, "kev": 0, "other": 6}}, "data": [{"timestamp": "2026-08-25T16:06:27.086Z", "date_only": false, "value": "2026-08-25T16:06:27.086Z", "kind": "milestone", "label": "Reserved", "source": "cvelistv5", "record": "CVE-2026-79976", "field": "cveMetadata.dateReserved"}, {"timestamp": "2026-10-21T18:19:34.519Z", "date_only": false, "value": "2026-10-21T18:19:34.519Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-79976", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2026-10-21T18:19:34.519Z", "date_only": false, "value": "2026-10-21T18:19:34.519Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / zephyr", "record": "CVE-2026-79976", "field": "containers.cna.providerMetadata.dateUpdated"}, {"timestamp": "2026-10-21T19:17:04.060Z", "date_only": false, "value": "2026-10-21T19:17:04.060", "kind": "milestone", "label": "Published", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-79976", "record": "FKIE_CVE-2026-79976", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2026-10-21T20:08:29.367Z", "date_only": false, "value": "2026-10-21T20:08:29.367585Z", "kind": "sighting", "label": "Seen", "source": "https://infosec.exchange/users/cve/statuses/117480705804331464", "record": "CVE-2026-79976", "field": "creation_timestamp", "uuid": "7123e7cb-9196-4f46-88d8-55edc5f65527", "content": "CVE-2026-79976 NULL pointer dereference in the MCTP I2C+GPIO target binding triggerable by a peer I2C controller The MCTP-over-I2C+GPIO target binding in subsys/pmci/mctp/mctp_i2c_gpio_target.c emulates a small pseudo-register file, where the bus controller first writes a register number and then writes or reads payload bytes. The selected register (b->reg_addr) and the data-phase flag (b->rxtx) were never cleared when the controller issued an I2C STOP, so after a completed transfer the target still had a data register selected while the packet buffer that register refers to had already been consumed and set to NULL by mctp_i2c_gpio_target_stop().\nA controller on the bus can re-enter the same branch of mctp_i2c_gpio_target_stop() with a NULL buffer using two ordinary transactions and no authentication: first a normal packet write to MCTP_I2C_GPIO_RX_MSG_ADDR followed by STOP (which delivers and frees b->rx_pkt), then a bare read transaction followed by STOP. The failing read_requested() call leaves the stale state untouched and the I2C driver still delivers the STOP callback, which then calls mctp_bus_rx() with a NULL packet. The symmetric case exists on the transmit side, where the stale MCTP_I2C_GPIO_TX_MSG_ADDR selection dereferences b->tx_pkt->end after b->tx_pkt has been cleared and additionally signals b->tx_complete a second time, causing the next outbound packet to be dropped.\nThe dereference happens in the I2C target interrupt handler, so on any target that traps accesses to address 0 the result is a fatal exception and a device reset or halt \u2014 a denial of service inflicted by any device able to act as controller on the shared management bus (for example compromised firmware on a peer MCTP endpoint or on the BMC). On parts where address 0 is readable, the impact degrades to a malformed packet buffer being handed to the MCTP stack and lost transmit packets. No attacker-controlled value is written and no confidentiality or integrity boundary is crossed.\nThe fix resets b->reg_addr to MCTP_I2C_GPIO_INVALID_ADDR and clears b->rxtx at every STOP, so a new register must be selected before any data phase can run again. Only builds that opt into the experimental CONFIG_MCTP subsystem with CONFIG_MCTP_I2C_GPIO_TARGET=y are affected.\nhttps://www.cve.org/CVERecord?id=CVE-2026-79976https://github.com/zephyrproject-rtos/zephyr/commit/60f7fee438504de29f2473d7a8d0535235b983efhttps://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-76fx-m4mf-24gq#zephyrproject #zephyr#CVE_2026_79976#bot", "url": "https://infosec.exchange/users/cve/statuses/117480705804331464"}, {"timestamp": "2026-10-23T20:43:08.859Z", "date_only": false, "value": "2026-10-23T20:43:08.859407Z", "kind": "other", "label": "Recorded", "source": "cvelistv5 / CISA-ADP", "record": "CVE-2026-79976", "field": "containers.adp.0.metrics.0.other.content.timestamp"}, {"timestamp": "2026-10-23T20:43:08.859Z", "date_only": false, "value": "2026-10-23T20:43:08.859407Z", "kind": "other", "label": "Recorded", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-79976", "record": "FKIE_CVE-2026-79976", "field": "metrics.ssvcV203.0.ssvcData.timestamp"}, {"timestamp": "2026-10-23T21:27:29.128Z", "date_only": false, "value": "2026-10-23T21:27:29.128Z", "kind": "other", "label": "Updated", "source": "cvelistv5", "record": "CVE-2026-79976", "field": "cveMetadata.dateUpdated"}, {"timestamp": "2026-10-23T21:27:29.128Z", "date_only": false, "value": "2026-10-23T21:27:29.128Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / CISA-ADP", "record": "CVE-2026-79976", "field": "containers.adp.0.providerMetadata.dateUpdated"}, {"timestamp": "2026-10-23T22:17:01.197Z", "date_only": false, "value": "2026-10-23T22:17:01.197", "kind": "other", "label": "Updated", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-79976", "record": "FKIE_CVE-2026-79976", "field": "lastModified"}], "metrics": {"as_of": "2026-11-01T22:51:52.911Z", "anchors": {"origin": {"timestamp": "2026-10-21T18:19:34.519Z", "date_only": false, "value": "2026-10-21T18:19:34.519Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-79976", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "discovery": null, "report": null, "acknowledgement": null, "disclosure": {"timestamp": "2026-10-21T18:19:34.519Z", "date_only": false, "value": "2026-10-21T18:19:34.519Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-79976", "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": 966738.392546, "hours": 268.53844237388887, "days": 11.189101765578704, "min_seconds": 966738.392546, "max_seconds": 966738.392546, "approximate": false, "ongoing": true, "order_known": true, "batch_listing": false, "end_before_start": false, "start": {"timestamp": "2026-10-21T18:19:34.519Z", "date_only": false, "value": "2026-10-21T18:19:34.519Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-79976", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "end": {"timestamp": "2026-11-01T22:51:52.911Z", "date_only": false, "label": "As of", "source": "Calculation clock"}}, "exploitation_to_patch": {"available": false, "missing": ["start"]}, "exploit_publication_to_patch": {"available": false, "missing": ["start"]}}}