On Fri, 13 Nov 2026 05:45:05 GMT, Timofei Fedotov <[email protected]> wrote:
> convolveBI() and convolveRaster() entry points read kern[klen - 1] without > requiring a nonempty kernel array. > > In JDK 25 and earlier, new Kernel(0, 0, new float[0]) is accepted by the > constructor. If this reaches the native convolution code, kern[klen - 1] > becomes kern[-1], an out-of-bounds read. > > JDK 26 added dimension validation to the Kernel constructor (JDK-8368729), > but the native methods still read the dimensions and coefficient array > directly from the object's fields. Inconsistent values can also be supplied > through reflection. > > Both methods should reject invalid kernel dimensions and array lengths before > accessing the coefficients. > > --------- > - [x] I confirm that I make this contribution in accordance with the [OpenJDK > Interim AI Policy](https://openjdk.org/legal/ai). Aside from breaking module encapsulation and updating non-exported variables, how else might this happen ? Is there anything that makes this case special ? I don't think we have a general need to defend against code that breaks encapsulation. There'd be no end to that impossible task. ------------- PR Comment: https://git.openjdk.org/jdk/pull/33887#issuecomment-6865058118
