{
  "id": "CVE-2026-79976",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-79976",
  "published_at": "2026-10-21T18:19:34.519Z",
  "title": "NULL pointer dereference in the MCTP I2C+GPIO target binding triggerable by a peer I2C controller",
  "vendor": "zephyrproject",
  "product": "zephyr",
  "cvss": {
    "score": 7.1,
    "source": "cna",
    "vector": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "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-\u003ereg_addr) and the data-phase flag (b-\u003erxtx) 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().\n\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-\u003erx_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-\u003etx_pkt-\u003eend after b-\u003etx_pkt has been cleared and additionally signals b-\u003etx_complete a second time, causing the next outbound packet to be dropped.\n\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 — 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.\n\nThe fix resets b-\u003ereg_addr to MCTP_I2C_GPIO_INVALID_ADDR and clears b-\u003erxtx 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.",
  "cwe": "CWE-476",
  "cvss_by_source": {
    "cna": 7.1
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "zephyrproject",
        "product": "zephyr",
        "ranges": [
          "\u003e= 4.3.0, \u003c 4.3.2",
          "\u003e= 4.4.0, \u003c 4.5.0"
        ],
        "fixed_in": [
          "4.3.2",
          "4.5.0"
        ]
      }
    ],
    "upgrade": [
      "Upgrade zephyr to 4.3.2 or 4.5.0 or later."
    ],
    "references": [
      {
        "kind": "Patch",
        "url": "https://github.com/zephyrproject-rtos/zephyr/commit/60f7fee438504de29f2473d7a8d0535235b983ef"
      },
      {
        "kind": "Patch",
        "url": "https://github.com/zephyrproject-rtos/zephyr/commit/a097178023785f3bc0a925ac489e490521ca84ea"
      },
      {
        "kind": "Vendor advisory",
        "url": "https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-76fx-m4mf-24gq"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
