Latest Linux and open source news from around the web

Keychron V3 Mechanical Keyboard Sponsored · View on Amazon → CanaKit Raspberry Pi 5 Starter Kit Sponsored · View on Amazon →
Phoronix

NVIDIA-VAAPI-Driver 0.0.17 Fixes Support For GB10 Powered Systems

The open-source, community-developed NVIDIA-VAAPI-Driver that provides a Video Acceleration API (VA-API) implementation built atop NVIDIA's NVDEC video decode interface is out with a new release. This is the open-source project that's motivated by getting accelerated video decoding to work within Mozilla Firefox and other apps when running with NVIDIA's packaged Linux driver...

Phoronix

Linux Enables Auto Counter Reload "ACR" For Intel Xeon Diamond Rapids

Merged as part of the perf subsystem fixes overnight is enabling Auto Counter Reload (ACR) functionality for upcoming Intel Xeon Diamond Rapids processors. This ACR enabling for Diamond Rapids "DMR" is happening in time for Linux 7.1-rc3 on Sunday while the work is also marked for back-porting to existing stable kernels...

Foss Force

A Simple One Click Mitigation for ‘Copy Fail’ and ‘Dirty Frag’ for Debian, Ubuntu, Mint, and Other Debian‑Based Distros

A trusted Debian dev turns scary new kernel bugs into a temporary two‑click fix until distros ship permanent patches. The post A Simple One Click Mitigation for ‘Copy Fail’ and ‘Dirty Frag’ for Debian, Ubuntu, Mint, and Other Debian‑Based Distros appeared first on FOSS Force.

LWN.net

More stable kernels with partial Dirty Frag fixes

Greg Kroah-Hartman has released the 6.1.171, 5.15.205, and 5.10.255 stable kernels, quickly followed by 6.1.172 and 5.15.206 kernels. This is another round of stable kernels to provide fixes for one of the CVEs (CVE-2026-43284) assigned following the Dirty Frag and Copy Fail 2 security disclosures. There is not, yet, a stable kernel with a fix for CVE-2026-43500, though a patch to fix the second half is in the works.

LWN.net

[$] Forgejo "carrot disclosure" raises security questions

An unusual, some might say hostile, approach to disclosing an alleged remote-code-execution (RCE) flaw in the Forgejo software-collaboration platform has sparked a multifaceted conversation. A so-called "carrot disclosure" in April has raised questions about the researcher's methods of unveiling a security problem, Forgejo's security policies, and the project's overall security posture.