Linux Journal

by George Whittaker

The Fedora Project has officially released Fedora Linux 45 Beta, giving users an early look at the technologies expected to form the foundation of the final Fedora 45 release. The beta became available on September 15, 2026, after Fedora's Quality team approved Release Candidate 1.3 for publication.

Fedora 45 Beta brings significant changes throughout the operating system, including Python 3.15, GCC 16.2, glibc 2.44, GNU Binutils 2.47, Go 1.27, LLVM 23, Podman 6, stricter RPM signature verification, improved DNF5 protections, a new userspace virtual console, standardized desktop secret storage, and substantial installer improvements.

The release is available across Fedora Workstation, KDE Plasma Desktop, Server, Cloud, IoT, Atomic Desktops, Spins, and Labs, although a few prerelease images are excluded.

Fedora 45 Beta Is Now Available

Fedora Linux 45 Beta represents the final major public testing milestone before Fedora 45 reaches stable status.

Fedora describes its beta releases as code-complete previews that closely represent what users should expect from the final version. Development isn't finished, however, and bugs or incomplete migrations can still be discovered during real-world testing.

Fedora 45 Beta is currently available in several major editions:

• Fedora Workstation 45 Beta
• Fedora KDE Plasma Desktop 45 Beta
• Fedora Server 45 Beta
• Fedora Cloud 45 Beta
• Fedora IoT 45 Beta
• Fedora Atomic Desktops
• Fedora Spins
• Fedora Labs

Existing Fedora installations can also be upgraded to the beta using Fedora's DNF system-upgrade process.

Fedora's official Workstation download page confirms Beta 1.3 images for both x86_64 and AArch64 systems.

A New Virtual Console with kmscon

One of Fedora 45's more unusual system-level changes is the replacement of the traditional in-kernel console with kmscon.

Fedora describes kmscon as a modern userspace virtual terminal implementation that provides smoother rendering, better internationalization and font handling, improved visual integration, and security improvements compared with the older console infrastructure.

This affects the virtual terminals users encounter outside their normal graphical desktop session.

Most desktop users spend relatively little time interacting directly with these consoles, but they remain important for troubleshooting, system administration, servers, recovery operations, and systems running without a graphical environment.

Moving that functionality into userspace also gives Fedora more flexibility for future development instead of relying entirely on the legacy kernel console implementation.

Go to Full Article

by George Whittaker

The Thunderbird team has officially released Thunderbird 156, bringing another round of new features, security improvements, authentication enhancements, and reliability fixes to the popular open-source email client. Released on September 15, 2026, the update is available for Linux alongside Windows and macOS.

Thunderbird 156 is not a dramatic redesign of the desktop mail client. Instead, it concentrates on improving areas that matter to everyday users and system administrators, including OAuth authentication, OpenPGP, POP3, IMAP, Exchange Web Services, SMTP, attachments, calendars, enterprise policies, and security.

For Linux users in particular, the release delivers several fixes affecting common mail protocols and account configurations while retaining support for Linux environments using GTK+ 3.14 or newer.

Thunderbird 156 Arrives on Linux

Thunderbird 156 follows version 154, which arrived in August with features including optional system tray operation and Microsoft Graph support for Microsoft 365.

Version 156 continues the project's monthly release cycle with a more targeted collection of authentication, security, compatibility, and reliability improvements.

According to Thunderbird's official release notes, version 156 requires:

• Linux: GTK+ 3.14 or newer
• Windows: Windows 10 or newer
• macOS: macOS 10.15 or newer

Thunderbird 156 was officially released on September 15.

Linux distribution availability will vary because distributions can package Thunderbird according to their own schedules. Users receiving Thunderbird through another packaging channel may therefore see version 156 at a different time.

Custom OAuth Support Expands

One of the most significant areas of development in Thunderbird 156 is OAuth authentication.

Thunderbird now supports custom OAuth configurations containing an issuer ID and client secret for IMAP and POP3 accounts. Custom OAuth support has also been extended specifically to POP3.

OAuth has become increasingly important as email providers move away from conventional username-and-password authentication toward token-based authentication.

For Thunderbird, broader custom OAuth support means users and organizations have greater flexibility when connecting the client to mail services that don't fit Thunderbird's predefined provider configurations.

This can be particularly useful in enterprise environments, self-hosted infrastructure, and organizations operating their own identity systems.

Exchange Custom OAuth Setup Fixed

Exchange users receive an important related correction.

Go to Full Article

by George Whittaker

The KDE Project has officially released KDE Plasma 6.7.5, delivering another round of bug fixes and stability improvements for the Plasma 6.7 desktop series. Released on September 8, 2026, the update contains roughly a month of fixes and updated translations contributed since Plasma 6.7.4 arrived in early August.

Unlike a major Plasma release, version 6.7.5 doesn't introduce a large collection of new desktop features. Instead, KDE has focused on fixing problems affecting Discover, KWin, Wayland, networking, System Monitor, Plasma Desktop, RPM-OSTree systems, Snap updates, HDR rendering, and several other components.

For users already running Plasma 6.7, this makes version 6.7.5 primarily a maintenance upgrade intended to make the desktop more dependable ahead of the next major Plasma series.

KDE Plasma 6.7.5 Arrives as the September Bugfix Release

KDE describes Plasma 6.7.5 as its September bugfix release for the Plasma 6 desktop.

The broader Plasma 6.7 series originally arrived in June 2026, followed by a succession of maintenance releases:

• Plasma 6.7.1 on June 23
• Plasma 6.7.2 on June 30
• Plasma 6.7.3 on July 14
• Plasma 6.7.4 on August 4
• Plasma 6.7.5 on September 8

KDE's official download infrastructure confirms that the Plasma 6.7.5 source packages became available on September 8.

This slower maintenance cadence later in a Plasma series is normal. Once the most urgent post-release problems have been addressed, KDE generally shifts more development attention toward the next feature release while continuing to provide important fixes for the current branch.

Discover Receives Several Important Fixes

KDE's Discover software center receives some of the most noticeable improvements in Plasma 6.7.5.

One particularly annoying problem could cause Discover to become stuck while checking for updates when its Snap backend was installed but no Snap applications actually had updates available.

That problem has now been corrected.

Discover also behaves more reliably when fwupd, the Linux firmware update service, is unavailable. Previously, a broken or intentionally masked fwupd service could interfere with Discover's normal operation. Plasma 6.7.5 allows the rest of the application to continue functioning correctly in that situation.

This is useful for systems where firmware updating isn't supported, where administrators intentionally disable the service, or where fwupd encounters a configuration problem.

Firmware Updates No Longer Incorrectly Require Reboots

Another Discover correction addresses a regression involving firmware updates.

Go to Full Article

by George Whittaker

One of Linux's oldest surviving distributions is moving closer to its next major release. Slackware 16 Alpha 1 became available on September 5, 2026, marking the first formal alpha milestone on the road toward Slackware Linux 16. The release follows a major rebuild of Slackware-current using a substantially newer GNU toolchain and brings together several upgrades that have accumulated since Slackware 15.0 arrived more than four years ago.

The alpha combines Linux 6.18 LTS, GCC 16.2.0, glibc 2.44, GNU Binutils 2.47, KDE Plasma 6, and numerous updated user-space packages while retaining much of the deliberately traditional architecture that has distinguished Slackware for decades.

For longtime Slackware users, Alpha 1 is particularly significant because it provides the clearest indication yet that the lengthy Slackware 16 development cycle is moving toward an eventual stable release.

Slackware 16 Finally Reaches Alpha

Slackware doesn't operate according to the predictable six-month or annual release schedules used by many other Linux distributions.

Instead, development takes place continuously through the Slackware-current branch. Patrick Volkerding and other contributors update that development tree until it reaches a state considered suitable for a stable release.

The previous major version, Slackware 15.0, was released in February 2022. More than four and a half years later, Slackware-current has now officially reached the first alpha milestone for version 16.

Volkerding marked the milestone following a complete rebuild of the distribution with its newly upgraded compiler, C library, and binary utilities.

The short changelog announcement even suggested there might finally be "a light at the end of the tunnel," a promising indication for Slackware users waiting for version 16.

The Entire Distribution Was Rebuilt

One of the most consequential changes behind Alpha 1 is a complete package rebuild.

Slackware's development toolchain has moved to:

• GCC 16.2.0
• glibc 2.44
• GNU Binutils 2.47

After introducing those components, Slackware rebuilt the distribution's packages against the updated environment.

A full rebuild is much more significant than simply replacing three packages.

GCC is responsible for compiling much of the software distributed with Slackware, glibc provides fundamental C library functionality used throughout Linux user space, and Binutils supplies essential development utilities including the GNU assembler and linker.

Rebuilding the distribution against these versions gives Slackware 16 a considerably newer foundation than its predecessor.

Go to Full Article

by Malana VanTyler

These platforms help teams monitor how technical content appears in AI-generated answers, from brand mentions and citations to accuracy and referral traffic.

Search is splitting into two experiences: one built around ranked pages and another around generated answers. As AI platforms summarize Linux tutorials, open-source project documentation, API references and technical guidance, teams need ways to measure whether their content is mentioned, cited and accurately represented.

An AEO platform provides that visibility. They help writers, maintainers, developers, and content teams examine how pages appear in generated answers, which sources receive citations, and whether AI platforms send traffic to the intended documentation.

Top AEO Tools for Technical Content

AEO and AI visibility platforms vary greatly. Some are mostly about tracking mentions, while others combine AI visibility with citations, referral traffic, competitor data or content recommendations. Below is a selection of tools, both popular and niche, that can be used by technical and content teams responsible for developer portals, Linux resources and open-source projects.

1. Similarweb AI Search Intelligence

Best for: Measuring AI visibility, citations and resulting website traffic in one platform.

Similarweb AI Search Intelligence gives teams a broad view of how brands and websites appear across AI-generated search experiences. It can be used to monitor brand mentions, citation frequency, prompt-level visibility and share of voice while comparing results with competitors. Similarweb also connects those measurements with its wider web and traffic intelligence, helping teams examine whether visibility and citations are producing visits to particular pages.

For technical content teams, this combination can make it easier to trace the path from an AI answer to its cited source and then to referral traffic. Teams can identify prompts where documentation is absent, determine which domains are being cited instead, and investigate whether AI-referred visitors reach the intended technical

pages. For example, an open-source project could examine whether prompts about installation on Ubuntu, package dependencies or command-line configuration lead users to its current documentation rather than an outdated forum post.

Standout feature: Similarweb combines AI visibility, citation analysis and traffic intelligence, reducing the need to examine those signals in separate platforms.

2. Rankscale.ai

Best for: Tracking technical content across a wide selection of AI engines.

Go to Full Article

by Malana VanTyler

AI security means hardening everything around the model, not just the model itself.

AI workloads have moved out of the research sandbox and into production, which means they now carry the same operational weight as any other critical service. If you want to understand what is AI security in practical terms, start here. It's not a 

separate discipline bolted onto your existing stack. It's an extension of it. The systems around a model matter as much as the model itself, and for teams running Linux and open-source infrastructure, that means applying familiar discipline to some new risks.

AI Security Is Becoming Part of the Linux Infrastructure

Treat AI workloads like production infrastructure, not side projects. A model doesn't run in isolation. It depends on an operating system, a container runtime, storage, APIs, identity systems, and a pile of dependencies. If any of those layers are weak, prompt filtering or output moderation won’t be enough.

Security teams that only look at the model may miss much of the actual attack surface. The work starts with the same questions you'd ask about any service. What's exposed? Who can reach it? What happens if it's compromised? 

The AI Attack Surface Extends Beyond the Model 

Model-serving APIs, embeddings, retrieval systems, vector databases, plugins, and CI/CD pipelines all now sit inside the perimeter. A vector database that holds proprietary documents is a data store like any other and needs the same access controls. An inference endpoint that accepts arbitrary text input is a public-facing service, and it needs rate limits and authentication like any other. Plugins and tool integrations expand what a model can touch, which also expands what an attacker can touch. It’s the same threat modeling you’d apply to a web application. 

Go to Full Article

by George Whittaker

Why security buyers are rethinking what matters most.

Security teams typically don’t struggle to find vulnerabilities as much as they have in the past. The harder part usually begins after the report arrives, once dozens of findings land in front of engineering teams already juggling patch schedules, production deadlines, and internal disagreements about urgency. Platforms like XBOW, OffSec, and Cobalt have entered that environment as organizations started rethinking what they actually need from pentesting vendors beyond annual compliance exercises.

A vulnerability may look severe inside a dashboard, while no one internally agrees whether it creates meaningful exposure or simply adds another item to an already crowded queue. Infrastructure also changes too quickly for static testing cycles to answer every operational question.

APIs update mid-quarter, contractors receive temporary access that lingers longer than expected, and cloud permissions change quietly during routine development work. Buyers evaluating vendors now spend more time asking whether testing accurately reflects the systems employees use every day.

Pentesting Vendors Now Face Different Expectations

Long reports stopped carrying the same weight years ago. Security teams already know modern environments contain weaknesses. What many organizations want now is clearer evidence showing which findings deserve immediate attention and which ones can wait without creating major operational exposure. That distinction became harder to ignore as remediation timelines stretched across larger environments.

Go to Full Article

by George Whittaker

Linux kernel developers are considering a new “steal governor” designed to improve performance when multiple virtual machines compete for limited physical CPU resources. The proposal uses the amount of CPU steal time observed inside a guest to dynamically reduce or expand the number of virtual CPUs on which that VM prefers to schedule work.

The feature is primarily aimed at heavily virtualized servers where administrators deliberately assign more virtual CPUs than the host can physically execute at once. Under heavy load, that overcommitment can lead to frequent vCPU preemption, lock-holder delays, cache disruption, and ultimately lower overall throughput.

The latest v11 patch series was posted on August 25, 2026, and its developer has proposed consideration during the Linux 7.3 development cycle, potentially targeting Linux 7.4 for inclusion. This means the feature is still under review and is not part of a stable Linux kernel yet.

What Is CPU Steal Time?

CPU steal time is a concept specific to virtualization.

Imagine a virtual machine has eight vCPUs. From inside that VM, the operating system behaves as though those eight CPUs are available. But those virtual CPUs ultimately need to run on the host's physical processors.

If several VMs are competing for the same physical CPU resources, the hypervisor may temporarily prevent one VM's vCPU from running so another VM can use the processor.

The time during which the guest wanted to execute but couldn't because the hypervisor was using the underlying CPU elsewhere is known as steal time.

High steal time is therefore a useful indication that the physical host is experiencing CPU contention.

The “Noisy Neighbor” Problem

The steal governor is designed primarily to address what virtualization engineers commonly call the noisy neighbor problem.

Consider a server hosting several VMs:

• VM A has 32 vCPUs.
• VM B has 32 vCPUs.
• VM C has 32 vCPUs.
• The physical server has only 64 CPU threads available to those workloads.

That configuration can work perfectly well when the VMs aren't simultaneously busy.

If all three suddenly become heavily loaded, however, they may collectively request more CPU time than the physical machine can provide.

The hypervisor then has to constantly switch between vCPUs.

Those interruptions can become particularly expensive if a vCPU is preempted while holding a lock or executing another latency-sensitive section of code. Other threads may then wait for a vCPU that isn't currently being allowed to run.

The result can be counterintuitive: giving the VMs more virtual CPUs can sometimes make the combined workloads slower.

Go to Full Article

by George Whittaker

The Thunderbird team has officially released Thunderbird 154, delivering several useful new features alongside a substantial collection of fixes for email, calendars, address books, authentication, and stability. Released on August 18, 2026, Thunderbird 154 is now the latest monthly release of the popular open-source email client.

For Linux users, one of the most interesting additions is a new optional system tray mode, while Microsoft 365 users gain Microsoft Graph support. The release also improves global search, attachment handling, IMAP reliability, Exchange authentication, and CalDAV synchronization.

New Optional System Tray Mode

One of Thunderbird 154's most welcome additions is an optional system tray mode.

When enabled, closing Thunderbird's last window no longer needs to completely terminate the application. Instead, Thunderbird can remain running in the background through the system tray.

This can be particularly useful for users who want Thunderbird available throughout the day without keeping its main window open.

For Linux desktop users, the feature could make Thunderbird feel more like a traditional background email client, especially on desktops where tray-based applications remain part of the normal workflow.

Microsoft Graph Enabled for Microsoft 365

Thunderbird 154 also enables Microsoft Graph for Microsoft 365.

Microsoft Graph is Microsoft's API platform for accessing Microsoft 365 services and data. Its integration is particularly important as Thunderbird continues improving its support for Exchange and Microsoft-hosted email environments.

Thunderbird has been steadily expanding its Microsoft ecosystem compatibility, making the open-source client increasingly practical for users who need to access workplace Microsoft 365 accounts from Linux.

Global Search Gets a Useful New Option

Thunderbird's global search functionality also receives an improvement.

Users can now configure global search results to open in list view by default, providing another option for people who prefer a more traditional message-list workflow when reviewing search results.

It's a relatively small addition, but one that can make repeated searches more convenient for users managing large mailboxes.

Better Attachment Management

Thunderbird 154 introduces several improvements for handling email attachments.

A new "Copy To" folder context menu has been added for message/rfc822 attachments, and these attached messages can now be dragged directly into Thunderbird's folder tree.

These changes should make it easier to organize attached email messages without having to use additional steps or workarounds.

Go to Full Article

by George Whittaker

Linux creator Linus Torvalds has officially released Linux Kernel 7.2, opening another chapter in the development of the world's most widely deployed open-source kernel. The final release arrived on August 16, 2026, following seven release candidates and roughly two months of development. Kernel.org now lists Linux 7.2 as the latest mainline release.

Linux 7.2 is a substantial update with improvements spanning CPU scheduling, storage performance, AMD and Intel hardware support, graphics, networking, virtualization, RISC-V, and Apple Silicon. Among its biggest additions are Cache-Aware Scheduling, USB4STREAM, AMD ISP4 support, and initial AMDGPU HDMI 2.1 FRL functionality.

Cache-Aware Scheduling Lands in Linux

One of the most interesting performance additions in Linux 7.2 is Cache-Aware Scheduling (CAS).

Modern processors frequently contain multiple last-level caches shared between groups of CPU cores. Traditional scheduling decisions don't always account optimally for those cache relationships, potentially moving tasks between cores in ways that increase cache misses.

Cache-Aware Scheduling gives the Linux scheduler additional information about cache topology so it can make smarter decisions about where workloads should run.

Early testing during development produced particularly impressive results for some server workloads, including major gains in certain MySQL configurations. The improvement varies significantly by hardware and workload, so users shouldn't expect similarly dramatic gains everywhere.

For modern AMD and Intel systems with increasingly complex CPU topologies, however, CAS provides another tool for extracting better performance from existing hardware.

USB4STREAM Enables High-Speed Connections Between Computers

Linux 7.2 also introduces USB4STREAM, an interesting new capability for transferring data directly between computers over USB4 or Thunderbolt connections.

Rather than treating USB primarily as a traditional host-to-device interface, USB4STREAM can facilitate high-speed communication between systems.

Potential applications include:

• Large file transfers
• Development environments
• High-speed system-to-system networking
• Debugging
• Specialized workstation workflows

With USB4 and Thunderbolt increasingly common on laptops and desktops, this could eventually become a useful option for moving large amounts of data between Linux machines.

AMD ISP4 Finally Reaches the Mainline Kernel

AMD users receive another important addition with the arrival of the AMD ISP4 driver.

ISP stands for Image Signal Processor, hardware responsible for processing camera data before it reaches applications.

Go to Full Article

by George Whittaker

Linux kernel developers made a significant last-minute graphics change for Linux 7.2, reverting the DRM GPU scheduler back to its previous FIFO policy by default after the newer fair scheduling implementation caused serious performance regressions. The revert was submitted just before the final Linux 7.2 release after users reported severe slowdowns and desktop freezes under sustained GPU workloads.

The decision demonstrates the kernel community’s conservative approach to regressions: when a new feature causes problems this late in a development cycle, restoring known-good behavior can be safer than rushing an incomplete fix.

What Changed in Linux 7.2?

Earlier in the Linux 7.2 development cycle, the DRM subsystem switched its default GPU scheduling policy to a new fair scheduler.

The goal was to distribute GPU execution time more fairly between competing workloads. Instead of relying on the established FIFO scheduling behavior, the new implementation uses a fairness-oriented approach designed to prevent one workload from dominating GPU resources.

However, real-world testing exposed problems that had not appeared during earlier development.

The final DRM fixes for Linux 7.2 therefore:

• Revert the fair scheduler changes
• Restore FIFO as the default
• Restore selectable scheduling policies
• Mark the fair scheduling policy as experimental

DRM maintainer Dave Airlie acknowledged that developers may have moved too aggressively when switching to the new scheduler.

AMD Radeon Gaming Exposed the Regression

The problem became particularly noticeable during gaming on an AMD Radeon RX 9070 XT.

A regression report described severe performance degradation when the GPU remained close to 100% utilization. A game running through Proton could drop to roughly 10 FPS or freeze, while audio continued playing normally.

The problem could become severe enough that the entire KDE Plasma Wayland session stopped responding, sometimes requiring the compositor to be killed or the computer to be rebooted.

Interestingly, reducing GPU load—such as by opening an in-game menu or switching away from the game—could immediately stop the stuttering.

FIFO Worked, FAIR Did Not

Testing provided strong evidence that the new scheduling policy was responsible.

The reporter compared Linux 7.2 release candidates using FAIR against configurations using the previous FIFO policy. Under otherwise similar conditions:

FAIR: reproduced the performance problem.

FIFO: survived extended stress testing without the regression.

Linux 7.1.x also behaved normally.

Go to Full Article

by George Whittaker

Intel’s open-source Linux graphics stack has taken another step forward with hardware-accelerated AV1 encoding through Vulkan Video. New code merged for Mesa’s ANV Vulkan driver enables the VK_KHR_video_encode_av1 extension on Intel’s DG2/Alchemist graphics hardware, including Arc A-Series GPUs.

The development expands Intel’s Vulkan Video capabilities on Linux and gives applications another standardized way to access the dedicated video encoding hardware found in modern Intel GPUs.

AV1 Encoding Arrives in Intel ANV

The key change is support for the Vulkan extension VK_KHR_video_encode_av1 in Mesa’s open-source Intel ANV driver.

The extension was finalized by the Khronos Group in 2024 and provides a standardized Vulkan interface for hardware-accelerated AV1 encoding. It complements Vulkan Video’s existing AV1 decoding support and means Vulkan can provide both encoding and decoding interfaces for AV1, H.264, and H.265.

Intel had previously stated that its Arc graphics products would support Vulkan Video AV1 encoding through a future software update.

Initially Targeting Intel Arc Alchemist

The newly enabled Linux support specifically targets DG2, better known commercially as Intel’s Arc Alchemist GPU generation.

These GPUs already contain dedicated hardware capable of AV1 encoding, so the Mesa update does not add AV1 capability through software. Instead, it provides Vulkan applications with another way to access the GPU’s existing hardware video engine.

That distinction is important because hardware encoding can deliver much better performance and efficiency than encoding AV1 entirely on the CPU.

Why AV1 Matters

AV1 has become increasingly important for streaming, screen recording, video conferencing, and online video distribution.

The codec can provide high image quality at relatively low bitrates, making it attractive for applications where bandwidth and storage efficiency matter. It is also royalty-free, which has helped encourage adoption throughout the open-source ecosystem.

Hardware AV1 encoding can be particularly useful for:

• Game streaming

• Desktop recording

• Live broadcasting

• Video conferencing

• Video transcoding

• Content creation

For Linux users with supported Intel Arc hardware, Vulkan Video now has the potential to provide a common API for these workloads.

Building on H.264 and H.265 Support

The AV1 work follows recent improvements to Intel’s Vulkan Video encoding support for other codecs.

Go to Full Article

by George Whittaker

A newly proposed patch for the Linux kernel's AMD P-State CPU frequency scaling driver is showing impressive gaming performance improvements, potentially delivering a noticeable boost for Ryzen users without requiring new hardware. Early benchmarks indicate that the optimization can significantly improve frame rates in CPU-bound games by allowing processors to respond more quickly to changing workloads. (phoronix.com)

Although the patch has not yet been merged into the mainline Linux kernel, the initial results have generated considerable excitement among Linux gamers and kernel developers alike.

What Is AMD P-State?

AMD P-State is the modern CPU frequency scaling driver for AMD Ryzen processors on Linux. Rather than relying on the older ACPI CPUFreq driver, AMD P-State communicates directly with the processor to adjust clock speeds based on workload demands.

Its goals include:

• Faster frequency scaling
• Improved power efficiency
• Better responsiveness
• Higher performance during demanding workloads
• Lower power consumption when the system is idle

Most modern Linux distributions already support AMD P-State on compatible Ryzen processors. (kernel.org)

A Focus on Gaming Performance

The new patch specifically targets how quickly AMD P-State responds when a game suddenly demands additional CPU performance.

Many games rapidly alternate between light and heavy CPU workloads. If the processor takes too long to increase its clock speed, short performance dips can occur.

The proposed optimization reduces that delay, allowing the CPU to boost more aggressively when needed and helping maintain smoother gameplay. (phoronix.com)

Promising Benchmark Results

According to early testing, the patch delivers meaningful improvements across several Linux gaming workloads.

Reported benefits include:

• Higher average frame rates
• Better 1% low FPS performance
• Faster CPU frequency response
• Improved responsiveness during gameplay
• More consistent frame delivery

The biggest gains appear in CPU-limited games where processor performance has a greater impact than GPU performance. Systems that are already GPU-bound may see smaller improvements. (phoronix.com)

Designed for Modern Ryzen CPUs

The patch targets systems using the AMD P-State driver, which supports many recent Ryzen processors.

Compatible platforms generally include:

Go to Full Article

by George Whittaker

Linux kernel developers are moving forward with plans to remove the crypto_rng API layer, a long-standing component of the kernel's cryptographic subsystem. The proposed change is part of a broader effort to simplify the kernel's internal architecture by eliminating redundant code paths and encouraging developers to rely on the kernel's modern random number generation interfaces instead. (phoronix.com)

Although the change happens entirely behind the scenes, it reflects the Linux kernel community's ongoing commitment to reducing technical debt, improving maintainability, and modernizing core infrastructure.

What Is the crypto_rng Layer?

The crypto_rng framework is an API within the Linux kernel's Crypto API that provides random number generation services for kernel components.

Historically, it allowed different kernel subsystems and drivers to request random data through a generic cryptographic interface. Over time, however, the kernel's dedicated random number generator has matured considerably, making much of the crypto_rng abstraction unnecessary. (kernel.org)

Today, developers generally recommend using the kernel's built-in random number generation functions directly instead of routing requests through the older crypto layer.

Why Developers Want to Remove It

According to discussions on the Linux kernel mailing list, the crypto_rng layer has become largely redundant.

Modern kernel code already relies on well-established interfaces such as:

• get_random_bytes()
• get_random_u32()
• get_random_u64()

These functions are maintained as part of the kernel's primary random number generation subsystem and are widely used throughout Linux. Maintaining an additional abstraction layer increases code complexity without providing significant practical benefits. (phoronix.com)

Removing unnecessary infrastructure also makes the kernel easier to maintain and audit over the long term.

Simplifying the Crypto API

The Linux Crypto API has evolved significantly over the years as new algorithms, hardware accelerators, and security features have been introduced.

Kernel maintainers have increasingly focused on:

Go to Full Article

by George Whittaker

The GNU Project has officially released GNU Binutils 2.47, the latest version of its essential collection of binary development tools for Linux and other Unix-like systems. The release delivers numerous bug fixes alongside new assembler, linker, and disassembler capabilities, expanded RISC-V support, reproducible source archives, and continued modernization of the GNU toolchain.

Used by developers worldwide, GNU Binutils forms a core part of the software development ecosystem, providing the low-level tools needed to assemble, link, inspect, and manipulate executable programs and object files.

What Is GNU Binutils?

GNU Binutils is a collection of command-line utilities that work closely with compilers such as GCC and Clang. While a compiler translates source code into object files, Binutils provides the tools needed to transform those object files into executable programs and libraries.

The package includes well-known utilities such as:

• ld (GNU Linker)
• as (GNU Assembler)
• objdump
• objcopy
• readelf
• nm
• strip
• ar
• strings

Together, these tools are used daily by Linux distributions, embedded developers, operating system projects, and software engineers building applications in C, C++, Rust, Go, and many other languages.

Expanded Support for RISC-V

One of the biggest improvements in Binutils 2.47 is expanded support for the rapidly growing RISC-V architecture.

The release adds support for several additional standard RISC-V extensions, allowing developers targeting modern RISC-V processors to work with newer instruction sets and hardware capabilities. These additions continue the GNU toolchain's strong commitment to one of the fastest-growing open processor architectures.

As more Linux distributions, development boards, and enterprise hardware adopt RISC-V, keeping development tools current is becoming increasingly important.

New Assembler Options

GNU Assembler (gas) gains several useful enhancements in version 2.47.

Among the most notable is a new command-line option:

• --reloc-section-sym=[all|internal|none]

This option gives developers finer control over how relocations referencing locally bound symbols are converted to section symbols, improving flexibility for certain assembly and linking workflows.

The release also introduces numerous assembler improvements across multiple CPU architectures.

Better Disassembly for AArch64

Developers working with Arm-based systems also benefit from new functionality.

Go to Full Article

by George Whittaker

After years of requests from the Linux gaming community, GOG has officially confirmed that it is developing native Linux support for the GOG Galaxy launcher. The announcement marks one of the biggest shifts in the company's history and signals a stronger commitment to Linux as a first-class gaming platform. While GOG has offered DRM-free Linux game downloads since 2014, its Galaxy launcher has remained exclusive to Windows and macOS—until now.

Although the company has not announced a release date, GOG says Linux has become a major area of investment, with development already underway.

A Long-Requested Feature Finally Becomes Reality

Native GOG Galaxy support has consistently ranked among the most requested features from Linux users. Until now, players who wanted to use Galaxy's library management, cloud saves, achievements, and automatic updates had to rely on compatibility layers or community-developed launchers.

In a statement to GamingOnLinux, GOG joint CEO Krzysztof Papliński said the company has hired a dedicated specialist and is actively exploring the best approach for bringing Galaxy to Linux. He described Linux as "one of the topics we hear the most about from our community," emphasizing that the project is now an active development priority.

Why GOG Galaxy Matters

Unlike the web-based game downloads that Linux users already have access to, GOG Galaxy serves as a full-featured game management application.

The launcher currently offers features including:

• Automatic game installation and updates
• Cloud save synchronization
• Achievement tracking
• Playtime statistics
• Game library organization
• Integrated storefront browsing
• Friends lists and social features
• Cross-platform launcher integration

Today, Linux users typically access these capabilities through community projects such as Heroic Games Launcher, Lutris, or Bottles. A native Galaxy client would provide an officially supported alternative with direct integration into GOG's ecosystem.

Linux Is No Longer an Afterthought

GOG's announcement reflects the growing importance of Linux gaming over the past several years.

The rapid adoption of Valve's Steam Deck, continuous improvements to Proton, and increasing hardware compatibility have significantly expanded Linux's role in PC gaming. As Linux's share of Steam users has grown, more developers and publishers have begun treating the platform as a viable target rather than a niche operating system.

For GOG, supporting Linux more fully aligns with its philosophy of giving users greater control over their purchased games.

Go to Full Article

by George Whittaker

Greg Kroah-Hartman has announced the release of Linux Kernel 7.1.4, the latest stable maintenance update for the Linux 7.1 series. As with other stable kernel releases, version 7.1.4 focuses on fixing bugs, improving hardware compatibility, and addressing security and reliability issues without introducing new features. The update became available on July 18, 2026, and users of the Linux 7.1 branch are encouraged to upgrade as soon as possible.

Rather than changing the kernel's feature set, Linux 7.1.4 delivers dozens of targeted fixes collected from developers across multiple kernel subsystems, helping ensure a more stable experience for desktops, servers, embedded devices, and cloud deployments.

Another Important Stable Maintenance Release

The Linux stable branch exists to provide safe updates between major kernel versions. Every stable release undergoes review before being published and contains fixes that have already been tested in the mainline kernel.

Linux 7.1.4 continues this process by incorporating patches that resolve regressions, improve system stability, and fix issues reported by users since the release of Linux 7.1.3.

For most users, these maintenance updates are recommended because they improve reliability without altering existing functionality.

Bug Fixes Across Multiple Kernel Subsystems

Like previous stable releases, Linux 7.1.4 includes fixes spanning many areas of the kernel.

The update addresses issues affecting:

• Memory management
• File systems
• Networking
• Device drivers
• Architecture-specific code
• Core kernel infrastructure
• USB and storage subsystems

These targeted patches help eliminate crashes, improve compatibility with newer hardware, and resolve edge cases that may only appear under specific workloads.

Improved Hardware Compatibility

One of the ongoing goals of Linux stable releases is expanding support for existing and newly released hardware.

Linux 7.1.4 includes updated drivers and compatibility fixes for various devices, helping improve support for:

• Graphics hardware
• Storage controllers
• Networking devices
• USB peripherals
• Laptop components
• ARM development boards

Although no major driver additions are expected in a maintenance release, incremental improvements like these often resolve hardware-specific bugs reported by users after earlier releases.

Security and Reliability Updates

Stable kernel releases also include security-related fixes that have been accepted into the maintenance branch.

Go to Full Article

by George Whittaker

Mozilla has officially released Firefox 153, bringing another round of improvements to its open-source web browser. The latest version introduces new multimedia capabilities, enhanced PDF editing tools, stronger privacy protections, better support for modern web technologies, and several features aimed at improving the browsing experience across Linux, Windows, and macOS. Firefox 153 became available on the stable release channel on July 21, 2026.

While this isn't a major redesign, Firefox 153 delivers a collection of practical updates that benefit both everyday users and web developers.

HDR Video Playback Comes to Windows

One of the headline features in Firefox 153 is support for High Dynamic Range (HDR) video playback on compatible Windows systems.

Users with HDR-capable displays and Windows HDR enabled can now enjoy richer colors, improved contrast, and brighter highlights when watching supported online video content. Mozilla notes that certain laptop displays offering only "HDR video streaming" are not currently supported, and some HDR videos recorded on mobile phones may still have limitations.

Although this feature is Windows-specific, it represents another step toward bringing Firefox in line with modern multimedia standards.

PDF Editing Becomes Even More Powerful

Mozilla continues expanding Firefox's built-in PDF editor, eliminating the need for third-party applications in many situations.

Firefox 153 introduces the ability to:

• Merge multiple PDF documents
• Insert images as new PDF pages
• Continue using existing editing tools such as annotations, page organization, and text editing

These additions make Firefox an even more capable document viewer and editor, especially for users who frequently work with PDF files.

Stronger Privacy and Permission Controls

Privacy remains one of Firefox's biggest selling points, and version 153 introduces several enhancements designed to give users more visibility and control over website permissions.

New improvements include:

• A visual indicator when a website is actively accessing your location
• More restrictive default permissions for browser extensions accessing local files
• Local Area Network (LAN) restrictions enabled by default for all users

These changes reduce unnecessary exposure of local resources while making it easier to understand what websites and extensions can access.

Experimental JPEG XL Support

Firefox 153 also adds experimental support for the JPEG XL image format, which many developers consider a promising successor to older image standards.

JPEG XL offers several advantages, including:

Go to Full Article

by George Whittaker

Sipeed has introduced NanoKVM-Go, a compact USB-C KVM-over-IP device that combines remote hardware management with AI integration. Designed for Linux, Windows, macOS, and other USB-C devices, NanoKVM-Go allows users to remotely view and control a system through a web browser while exposing its keyboard, mouse, and display functions to AI agents via the Model Context Protocol (MCP).

Unlike traditional KVM-over-IP solutions that require multiple cables and dedicated networking hardware, NanoKVM-Go simplifies the setup into a single USB-C connection, making remote administration and AI-assisted automation more accessible for developers, system administrators, and homelab enthusiasts.

A Portable USB-C KVM

NanoKVM-Go is roughly the size of a smartwatch, measuring about 45 × 40 × 15 mm, yet it combines several functions into a single device.

Key hardware features include:

• USB-C connection for video, audio, keyboard, mouse, and power
• Wi-Fi 6 connectivity
• Browser-based remote management
• Support for virtual USB storage
• Built-in Tailscale integration for secure remote access
• Fanless aluminum enclosure with low power consumption

Because it connects over USB-C using DisplayPort Alt Mode, the device can manage a wide variety of hardware without requiring software installation on the target system.

Designed for Linux and Beyond

NanoKVM-Go supports numerous USB-C devices, including:

• Linux desktops and laptops
• Windows PCs
• macOS systems
• Mini PCs
• Steam Deck
• Android devices with DisplayPort Alt Mode
• iPhone 15 and newer models
• Tablets supporting USB-C video output

For Linux users, this provides an easy way to perform BIOS configuration, operating system installation, kernel debugging, or remote troubleshooting—even when the operating system is unavailable.

AI Integration Through MCP

One of NanoKVM-Go's defining features is its AI-native design.

Rather than simply streaming a desktop remotely, the device exposes its KVM functions as an MCP (Model Context Protocol) server, allowing compatible AI agents to interact with the connected computer using hardware-level keyboard and mouse input.

This enables AI systems to:

• View the screen
• Move the mouse
• Type on the keyboard
• Launch applications
• Navigate user interfaces
• Complete repetitive desktop workflows

Because control happens at the hardware level, AI agents can interact with systems regardless of the operating system installed.

Go to Full Article

by George Whittaker

Artificial intelligence has helped uncover one of the most significant Linux kernel security flaws in recent years. Security researchers at Nebula Security announced the discovery of GhostLock (CVE-2026-43499), a critical local privilege escalation vulnerability that remained hidden in the Linux kernel for approximately 15 years before being identified by the company's AI-powered vulnerability research platform, VEGA.

The vulnerability affects Linux kernels dating back to version 2.6.39 (2011) and allows an unprivileged local user to obtain full root privileges on vulnerable systems. Its discovery not only highlights the importance of timely kernel updates but also demonstrates how AI is beginning to transform vulnerability research.

What Is GhostLock?

GhostLock is a use-after-free (UAF) vulnerability located in the Linux kernel's futex (fast userspace mutex) implementation.

Futexes are synchronization primitives that allow user-space applications to efficiently coordinate access to shared resources while minimizing expensive kernel interactions. Because they are widely used throughout Linux, any flaw within this subsystem can have broad security implications.

According to Nebula Security, incorrect handling of the remove_waiter() function can leave behind a dangling kernel pointer that an attacker can manipulate to execute arbitrary code with kernel privileges.

A Reliable Path to Root Access

One of the reasons GhostLock has attracted so much attention is the reported reliability of the exploit.

Researchers demonstrated that an attacker with nothing more than a standard local user account can escalate privileges to root in roughly five seconds, with a reported success rate of 97% on vulnerable systems.

Unlike many kernel exploits that are unstable or require highly specific system configurations, GhostLock appears to be both practical and repeatable, making it particularly concerning for administrators.

Container Escapes Are Also Possible

The implications extend beyond traditional Linux desktops and servers.

Researchers report that GhostLock can also be used to escape containers and compromise the underlying host operating system. Because containers share the host kernel, a successful privilege escalation inside a container can potentially grant root access to the host itself.

This makes the vulnerability especially important for environments running:

Go to Full Article