)]}'
{
  "commit": "441f99c90497e15aa3ad1dbabd56187e29614348",
  "tree": "bc57636479d687c706c17d6818e9593b498c7f9d",
  "parents": [
    "d041b557792c85677f17e08eee535eafbd6b9aa2"
  ],
  "author": {
    "name": "Romain Izard",
    "email": "romain.izard.pro@gmail.com",
    "time": "Tue Oct 31 15:42:35 2017 +0100"
  },
  "committer": {
    "name": "Herbert Xu",
    "email": "herbert@gondor.apana.org.au",
    "time": "Fri Nov 03 21:35:35 2017 +0800"
  },
  "message": "crypto: ccm - preserve the IV buffer\n\nThe IV buffer used during CCM operations is used twice, during both the\nhashing step and the ciphering step.\n\nWhen using a hardware accelerator that updates the contents of the IV\nbuffer at the end of ciphering operations, the value will be modified.\nIn the decryption case, the subsequent setup of the hashing algorithm\nwill interpret the updated IV instead of the original value, which can\nlead to out-of-bounds writes.\n\nReuse the idata buffer, only used in the hashing step, to preserve the\nIV\u0027s value during the ciphering step in the decryption case.\n\nSigned-off-by: Romain Izard \u003cromain.izard.pro@gmail.com\u003e\nReviewed-by: Tudor Ambarus \u003ctudor.ambarus@microchip.com\u003e\nCc: \u003cstable@vger.kernel.org\u003e\nSigned-off-by: Herbert Xu \u003cherbert@gondor.apana.org.au\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1ce37ae0ce565a130962f50244f331117fe965d8",
      "old_mode": 33188,
      "old_path": "crypto/ccm.c",
      "new_id": "0a083342ec8cf3b17c4da15c515c8c3d7a519a0f",
      "new_mode": 33188,
      "new_path": "crypto/ccm.c"
    }
  ]
}