)]}'
{
  "commit": "45af75d2af3b85af51bc0d16af5df30abff1935b",
  "tree": "1922ddeab229559a54bab2bd81178963563309ae",
  "parents": [
    "5de611be4ae149c3d83c9633c7b5350c11d73a3d"
  ],
  "author": {
    "name": "Michael Brown",
    "email": "mcb30@ipxe.org",
    "time": "Tue Aug 04 12:06:11 2026 +0100"
  },
  "committer": {
    "name": "Michael Brown",
    "email": "mcb30@ipxe.org",
    "time": "Tue Aug 04 12:21:46 2026 +0100"
  },
  "message": "[efi] Treat invalid device path components as ending the path\n\nEFI device paths generally have no externally defined length: the only\nway to calculate the length is to scan the device path itself (and\ntherefore to implicitly assume that the path is valid).\n\nThere is no way to guard against a malformed device path (absent the\natypical existence of an external length), but we can at least prevent\ninfinite loops from a device path component that encodes a zero\nlength.\n\nTreat any device path component with a length too short to contain the\ndevice path header as ending the device path.  This does not prevent\ninvalid device paths from being accepted, but it does at least guard\nagainst a silent system hang from an infinite loop, and ensures that\ncallers may safely subtract the length of the device path header from\nthe length of the path component without underflowing.\n\nSigned-off-by: Michael Brown \u003cmcb30@ipxe.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c474f40d8fb68f6896f482eb0eed772fc37db7b9",
      "old_mode": 33188,
      "old_path": "src/interface/efi/efi_path.c",
      "new_id": "0ed15def07f9613bfffeebc5de6b2b678b2d6e8a",
      "new_mode": 33188,
      "new_path": "src/interface/efi/efi_path.c"
    }
  ]
}