)]}'
{
  "commit": "ed9be64eefe26d7d8b0b5b9fa3ffdf425d87a01f",
  "tree": "69719f3d0c6436c8d4a21e506872dede9374f5be",
  "parents": [
    "a0312af1f94d13800e63a7d0a66e563582e39aec"
  ],
  "author": {
    "name": "Will McVicker",
    "email": "willmcvicker@google.com",
    "time": "Sat Dec 05 00:48:48 2020 +0000"
  },
  "committer": {
    "name": "Jiri Kosina",
    "email": "jkosina@suse.cz",
    "time": "Mon Jan 18 09:09:57 2021 +0100"
  },
  "message": "HID: make arrays usage and value to be the same\n\nThe HID subsystem allows an \"HID report field\" to have a different\nnumber of \"values\" and \"usages\" when it is allocated. When a field\nstruct is created, the size of the usage array is guaranteed to be at\nleast as large as the values array, but it may be larger. This leads to\na potential out-of-bounds write in\n__hidinput_change_resolution_multipliers() and an out-of-bounds read in\nhidinput_count_leds().\n\nTo fix this, let\u0027s make sure that both the usage and value arrays are\nthe same size.\n\nCc: stable@vger.kernel.org\nSigned-off-by: Will McVicker \u003cwillmcvicker@google.com\u003e\nSigned-off-by: Jiri Kosina \u003cjkosina@suse.cz\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4d0faf77c14bf4700b5b8517e7e933319e87f454",
      "old_mode": 33188,
      "old_path": "drivers/hid/hid-core.c",
      "new_id": "097cb1ee312684895ac7fd44860ee3d9faa4bd2d",
      "new_mode": 33188,
      "new_path": "drivers/hid/hid-core.c"
    }
  ]
}