The arrival de Table 25.3.5 This represents the last major release of the 25.3 branch before the highly anticipated 26.0 series takes over as the new stable version of the graphics stack. While it may seem like a minor update, it's actually a very polished maintenance point that includes a good number of critical fixes designed to provide maximum stability for those who prefer not to live on the edge with the latest versions.
This version focuses on Fix bugs, improve the reliability of Vulkan drivers (both for AMD, Intel, and Qualcomm), polish aspects of Vulkan Video, and add minor fixes to older drivers like R600. Furthermore, it's being released at a key moment in the Mesa release schedule, with a very active version history that continues to release branches 23.x, 24.x, and 25.x, and with the first Mesa 26 candidates already circulating. Many of these changes relate to new drivers and adjustments in previous branches that have paved the way.
Key new features of Mesa 25.3.5
Mesa 25.3.5's foundation is focused on stability, but that doesn't mean it's an irrelevant update. Among the most notable improvements are those related to Vulkan Video on RADV (AMD) and Intel ANV driversas well as multiple bug fixes distributed across various drivers, including R600, TURNIP (Qualcomm Adreno), and NVK. Specifically, the following are included: key arrangements in RADV and improved codec support.
As detailed in the release notes and third-party announcements, this version incorporates a wide assortment of different fixes for Intel and AMD Vulkan drivers, as well as some tweaks for older Radeon hardware. In addition, there are specific adjustments to how tile sizes are calculated for the video codec in RADV, and corrections to specific parameters such as maxActiveReferencePictures in H.264 decoding and a rather conservative decision by the Intel ANV driver regarding video encoding with Vulkan; in fact, just like in previous versions such as Table 25.2.6There is a tendency to prioritize stability over early exposure of functions.
The overall result is a version that directly targets those who need the most stable graphical environment possible, whether on desktop computers, laptops with integrated GPUs, or devices that rely on Qualcomm AdrenoIf you're coming from 25.3.4 or earlier within the same branch, it makes perfect sense to upgrade.
Changes in RADV and Vulkan Video (AMD)
One of the most developed areas in Mesa 25.3.5 is support for Vulkan Video about RADVThe Vulkan driver for AMD GPUs within Mesa. The original announcement text mentions that a "more reliable" method is now used to calculate tile sizes, which is crucial to ensuring that video decoding works without artifacts or unexpected crashes.
This change addresses problems detected in the previous calculation of these tiles, which could cause errors in accelerated video playback by GPU in certain hardware and codec combinations. By switching to a more robust calculation scheme, the risks of out-of-range reads, memory corruption, or subtle errors that later translate into video glitches are minimized.
In addition, a correction related to maxActiveReferencePictures in H.264 decoding within the Vulkan Video code of RADV. In codecs like H.264, the number of simultaneously active reference frames is a key parameter for the correct functioning of the decoding: if it is mismanaged, there may be dropped frames, stuttering, or even process crashes.
With these adjustments, Mesa 25.3.5 directly aims to improve the experience of those who use Linux as a multimedia platform and rely on GPU acceleration for playing H.264 contentIt's not a flashy interface change, but it's very important for day-to-day stability.
Intel ANV and disabling video encoding
On the Intel side, the notes highlight a striking move: the driver Intel ANV disables video encoding via Vulkan Video for the latest hardware generations, at least temporarily. Specifically, this refers to Meteor Lake, the Alchemist (Arc) discrete GPUs, and even newer hardware.
The main reason is that the implementation of Vulkan Video encoding It has not been sufficiently tested on those platforms. Instead of exposing potentially unstable functionality to users, the Mesa team has chosen to hide it until it is better tested and polished. It's a conservative decision, but a very sensible one if the goal is to give confidence to system administrators and advanced users; remember that changes related to a Very important patch for the Intel driver which also prioritized reliability.
This means that if you have a laptop or desktop computer with Intel Meteor Lake or an Arc GPU And since you depend on Mesa, in version 25.3.5 you won't find the Vulkan Video encoding feature available, although you will still be able to use the other capabilities of the ANV driver. This change does not affect decoding or the "normal" use of Vulkan for games and 3D applications.
Beyond this deactivation, the following are also integrated Several bug fixes in the ANV driver These fixes aren't detailed individually in the summary, but they are part of the "variety of other random bug fixes" mentioned. In practice, we can expect improved stability and stricter adherence to the Vulkan specification, which reduces the risk of crashes in demanding games or benchmarks.
General improvements to the RADV and ANV drivers
In addition to the specific changes in Vulkan Video, the Mesa 25.3.5 release includes a good handful of general fixes in the Vulkan drivers from AMD (RADV) and Intel (ANV). The announcement mentions "a variety of other random bug fixes," which typically cover everything from minor validation errors to corrections of regressions introduced in previous versions.
At RADV, these types of corrections usually have to do with specific game or application titles that exhibit unusual behavior (crashes, visual errors, synchronization problems, etc.). Often, these fixes are documented as specific patches for some graphics engines or for certain Vulkan extensions used extensively in AAA games.
At ANV, the approach is similar: to strengthen compliance with the Vulkan specification and to ensure that performance optimizations don't break anythingIt is common to see patches that prevent memory contentions, adjustments in the handling of complex graphics pipelines, or small optimizations that reduce driver overhead in certain situations.
The sum of all these small pieces makes 25.3.5 a key update for any Linux gamer. Modern AMD or Intel GPUsEven if you're not particularly concerned about the video aspect, a simple timing adjustment can often make the difference between a perfectly stable game and a nightmare of sporadic crashes.
Support for legacy hardware: R600 driver
Although much of the media focus is on Vulkan and current GPUs, this version also pays attention to an old acquaintance: the Gallium3D R600 driverThis driver covers older AMD/ATI Radeon HD 2000 through HD 6000 graphics cards, hardware that is still present in many recycled computers, secondary PCs, or veteran workstations.
The release notes indicate that Mesa 25.3.5 includes "a few fixes" for that driver, meaning that they continue to address specific issues even on hardware that's over a decade old. This reflects Mesa's philosophy quite well: not to completely abandon users of older GPUsalthough obviously the bulk of the development is focused on modern hardware and APIs like Vulkan.
In practice, these fixes can mean that a recent distro with an updated Mesa continues to have a low level of issues in systems with older Radeon HD graphics cardsWhether for desktop tasks, video playback, or even light gaming, it's not a revolutionary leap, but it's appreciated that compatibility doesn't break overnight.
TURNIP (Qualcomm Adreno), NVK and other drivers
Mesa 25.3.5 also brings new features for the mobile ecosystem and for NVIDIA GPU support via open-source drivers. Specifically, the following are mentioned: Several fixes in the TURNIP driver, responsible for Vulkan support for Qualcomm Adreno GPUs, which are very common in phones and some ARM devices.
These types of updates are primarily aimed at improving the stability in systems based on Qualcomm SoCswhich may be running conventional Linux, Android, or other variants. TURNIP has gained traction in recent years as a powerful open-source alternative to Vulkan on mobile devices, and each bug fix helps make the experience less dependent on proprietary drivers.
On the other hand, there is talk of "a few NVK fixes", that is, a few adjustments in NVKThe open-source Vulkan driver for NVIDIA GPUs within Mesa is still considered relatively new and is constantly evolving. These fixes typically focus on improving compatibility with games and benchmarks, as well as addressing gaps in the API implementation.
Taken together, these fixes in TURNIP, NVK, and other minor drivers round out the release so that Table 25.3.5 It should not only be an update focused on classic PCs, but also on ARM devices, lightweight laptops, and other platforms where open graphics support is especially critical.
Table 25.3.5 as part of a moving ecosystem
The release of Mesa 25.3.5 didn't come alone; it was accompanied and mentioned in broader contexts within the Linux ecosystem. Some news compilations, such as weekly summaries, included it. Weekly Roundup Specialized media outlets often group it with releases of other key projects such as GParted, Transmission, GStreamer, OpenSSL, Proton, VirtualBox, Calibre, Tails, Linux Lite, Shotcut, or TigerVNC.
Mesa's appearance on these lists reflects his enormous importance within the Linux graphics stackAlmost every modern Linux distribution relies on its drivers and OpenGL/Vulkan implementation to accelerate desktop, games, and multimedia performance. A simple bug fix release from Mesa can have a much greater impact than new features from smaller projects.
Additionally, the communication environment surrounding Mesa includes brief news items on the official website, mailing lists for launch announcements, and activity on social media where updates are sometimes shared. If JavaScript is disabled in your browser, some of these platforms will even notify you that Activate JS or use a compatible browserThis highlights the importance of dynamic web technologies today, even in such technical projects.
Why upgrade to Mesa 25.3.5
If you're already on Mesa 25.3, the short answer is that It makes perfect sense to updateThis version does not break compatibility, introduce drastic changes to APIs, and is limited to correcting bugs, reducing risks, and fine-tuning behavior in key drivers.
Those who use AMD GPUs with RADV benefit from Specific improvements in Vulkan Video and general fixes affecting both games and 3D applications. Intel users with ANV see their stability prioritized, even if it means temporarily forgoing Vulkan video encoding on newer platforms until everything is thoroughly tested.
Owners of older Radeon HD 2000-6000 hardware continue to receive Little pampering touches through the R600 driverMeanwhile, devices with Qualcomm Adreno and NVIDIA GPUs that utilize NVK also experience a slightly more robust environment. All in all, this makes 25.3.5 a highly recommended update in almost any scenario.
Furthermore, with Mesa 26.0 just around the corner, staying up-to-date within the 25.3 branch helps make the jump to the next stable series smoother. much smoother and more predictable, without carrying over old bugs that were already resolved in the last maintenance point.
With all of the above in mind, it can be said that Table 25.3.5 ends on a high note The final stage of the 25.3 branch: consolidates support for Vulkan Video on AMD, adopts a cautious stance with encoding on Intel ANV, takes care of users of older hardware through R600 and continues to polish drivers such as TURNIP and NVK, all framed within a frenetic release cycle that prepares the ground for Mesa 26.0 without neglecting, for a moment, the stability of the present.
