Package: openrazer / 3.5.1+dfsg-2+deb12u1
Metadata
Package | Version | Patches format |
---|---|---|
openrazer | 3.5.1+dfsg-2+deb12u1 | 3.0 (quilt) |
Patch series
view the series filePatch | File delta | Description |
---|---|---|
6322c4ab9d12b5711eead41821fe19149e515afc.patch | (download) |
Makefile |
2 0 + 2 - 0 ! |
[patch] debian: replace python packaging hacks It seems Debian setuputils can just use --install-layout=deb to move the files to the correct location. This allows us to remove the manual moving around of directories that was present until now. |
skip without CONFIG_USB.patch | (download) |
install_files/dkms/dkms.conf |
1 1 + 0 - 0 ! |
--- |
0001 driver Stop copying any custom frame data when param.patch | (download) |
driver/razerchromacommon.c |
6 3 + 3 - 0 ! |
driver: stop copying any custom frame data when parameters are invalid While the initial idea of this check was to sanitize any a row_length value which is too high. But in reality we should just essentially error out (which due to the function signature we can't do properly), and stop trying to memcpy any data. Issue: https://github.com/openrazer/openrazer/issues/2433 |
0002 driver Fix possible integer overflow in write_matrix.patch | (download) |
driver/razeraccessory_driver.c |
2 1 + 1 - 0 ! |
driver: fix possible integer overflow in write_matrix_custom_frame When a user passes start_col=0x00 and stop_col=0x55 with the data, row_length can easily wrap around leading to undesired behavior including out of bounds read while copying data into report.arguments. Avoid the overflow by making sure the underlying type has enough space for the value ((255 + 1) - 0) * 3 = 768. Issue: https://github.com/openrazer/openrazer/issues/2433 |