Debian Patches
Status for mesa/25.0.7-2+deb13u1
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| path_max.diff | no | |||||
| src_glx_dri_common.h.diff | no | |||||
| disable_ppc64el_assembly.diff | disable use of ppc64el assembly code | Dmitry Shachnev <mitya57@debian.org> | no | debian | 2025-02-02 | |
| etnaviv-add-support-for-texelfetch.patch | [PATCH 1/3] etnaviv: isa: Add txf instruction This instruction is used to implement texelfetch. Blob generates such txf's for dEQP-GLES3.functional.shaders.texture_functions.texelfetch.+ |
Christian Gmeiner <cgmeiner@igalia.com> | no | 2025-04-18 | ||
| Revert-hasvk-elk-stop-turning-load_push_constants-in.patch | Revert "hasvk/elk: stop turning load_push_constants into load_uniform" This reverts commit b036d2ded2de32e81730ec8ce37c803bad112efa. This seems to break gtk4 and other stuff. (taking ack from Lionel saying we should revert) (cherry picked from commit 870b8717b25eceadac8dd653debe8346826227cb) |
Dave Airlie <airlied@redhat.com> | no | 2025-06-09 | ||
| kopper-Revert-kopper-Explicitly-choose-zink.patch | kopper: Revert "kopper: Explicitly choose zink" This reverts commit 854bc2ee05f90e426f318352682144050e402d4b. Forcing zink explicitly would get zink-on-lvp picked up over llvmpipe for gbm dri support, which is not intended. Currently, zink_screen's choose_pdev won't be able to reject it when the driver name is explicit. So we have to revert the change first to mitigate regressions. (cherry picked from commit e6481d3f42e0cd735fda38fb3029e6f8abf5a0e6) |
Yiwei Zhang <zzyiwei@chromium.org> | no | 2025-05-17 | ||
| backport_STACK_ARRAY.patch | backport macro STACK_ARRAY, needed for fix for CVE-226-40393 | not-needed | https://gitlab.freedesktop.org/mesa/mesa/-/blob/f43cff3728e58c377d1e03b13db62514217abfe1/src/util/stack_array.h | 2026-05-25 | ||
| CVE-2026-40393-part1.patch | spirv: Use STACK_ARRAY instead of NIR_VLA The number of fields comes from the shader, so it could be a value large enough that using alloca would be problematic. (cherry picked from commit 3da828d2dd12e20ba2afc152db8d7236c7a48c13) |
Ian Romanick <ian.d.romanick@intel.com> | no | https://gitlab.freedesktop.org/mesa/mesa/-/commit/978fd42b4b7d1e9c0435ffa7e1a4d339cba9b76e | 2026-01-23 | |
| CVE-2026-40393-part2.patch | nir: Use STACK_ARRAY instead of NIR_VLA The number of fields comes from the shader, so it could be a value large enough that using alloca would be problematic. (cherry picked from commit 9017d37e84771f921a63676dd8b955df9ef20f29) |
Ian Romanick <ian.d.romanick@intel.com> | no | https://gitlab.freedesktop.org/mesa/mesa/-/commit/978fd42b4b7d1e9c0435ffa7e1a4d339cba9b76e | 2026-01-23 |
All known versions for source package 'mesa'
- 26.1.4-1 (sid)
- 26.1.2-1 (forky)
- 25.2.6-1~bpo13+1 (trixie-backports)
- 25.0.7-2+deb13u1 (trixie-proposed-updates)
- 25.0.7-2 (trixie)
- 25.0.7-2~bpo12+1 (bookworm-backports)
- 22.3.6-1+deb12u2 (bookworm-proposed-updates)
- 22.3.6-1+deb12u1 (bookworm)