)]}'
{
  "commit": "d15aa29e71753af50b7e03d77fddbe7fcae04884",
  "tree": "f324be447682bff2c11c6960f2e2a1874a6df222",
  "parents": [
    "e2a57cfb4d915b4ba820585aef9fdee7bca13fe5"
  ],
  "author": {
    "name": "Rudolf Polzer",
    "email": "rpolzer@google.com",
    "time": "Wed May 27 03:39:21 2026 -0700"
  },
  "committer": {
    "name": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Wed May 27 07:56:47 2026 -0700"
  },
  "message": "Fix uninitialized data read by AES-GCM-SIV assembly.\n\nNote that this data is later read by a vmovdqa op, but later shuffled\nout by a vpshufd op with mask 0x90. So there is currently no impact from\nthis issue - it however either should be clearly documented, or fixed,\nso let\u0027s just fix it to always have the CPU read \"predictable\" data.\n\nChange-Id: I937a429e484132efd08e7b494007b7d16a6a6964\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/95929\nPresubmit-BoringSSL-Verified: boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com \u003cboringssl-scoped@luci-project-accounts.iam.gserviceaccount.com\u003e\nReviewed-by: Adam Langley \u003cagl@google.com\u003e\nCommit-Queue: Rudolf Polzer \u003crpolzer@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "cc80306b28fc2811b61436398c4f16f0f8cc903e",
      "old_mode": 33188,
      "old_path": "crypto/cipher/e_aesgcmsiv.cc",
      "new_id": "8ee9c68cb3506ee1bc4ee5eb63aeeabe3eb3f6dc",
      "new_mode": 33188,
      "new_path": "crypto/cipher/e_aesgcmsiv.cc"
    }
  ]
}