The issue is caused by an incorrect state transition in the `parse char class()` function, leading to the possibility of using an uninitialized variable when writing to a buffer. This can result in a heap out-of-bounds write in the `bitset set range()` function during regular expression compilation, causing memory corruption. The estimated number of potentially affected devices worldwide is not specified. There is no information about real-world incidents where this issue was exploited.