GLib 2.31.8 and earlier, when the gstrhash function is used, computes hash values without restricting the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU consumption) via crafted input to an application that maintains a hash table. NOTE: this issue may be disputed by the vendor; the existence of the gstrhash function is not a vulnerability in the library, because callers of ghashtablenew and ghashtablenew_full can specify an arbitrary hash function that is appropriate for the application.