
What happened
Linus Torvalds debugged and fixed a kernel bug in Intel's Xe GPU driver where the driver incorrectly rounded up a memory address used for CCS (Compute Core Scratch) storage to the nearest 128kB boundary, causing the driver and hardware engine to write to memory outside that boundary. The fix was committed as a one-liner patch that prevents the driver from handing out the flat CCS storage as usable VRAM.
Why it matters
The bug caused kernel job timeouts that Torvalds could reproduce at will. When the misaligned memory happened to overlap with GPU page tables, it triggered severe corruption; when it overlapped other data, it caused random screen corruption. The issue originated in an earlier commit from two years ago but only became consistently reproducible recently due to a change in user space behavior.
What to watch
The patch addresses a longstanding memory alignment flaw in the Xe driver. Torvalds notes he spent a full day debugging the issue between merge window work, and the fix is expected to resolve both the predictable kernel timeouts and the occasional random screen corruption users had been experiencing.
Summaries like this, in your inbox every morning.
The bug represents a subtle but critical memory alignment issue in Intel's Xe GPU driver. The problem lay in how the driver managed memory stolen for CCS (Compute Core Scratch) — a performance feature used in modern Intel GPUs. By rounding up the memory address to a 128kB boundary without accounting for where that boundary fell, the driver inadvertently created a window where both the driver and the hardware engine could write to unallocated or already-allocated memory regions.
What made this bug particularly difficult to track was its non-deterministic impact. When the misaligned memory region overlapped with GPU page tables — the structures that map virtual memory to physical memory — the corruption was severe and immediate, manifesting as kernel timeouts. But in cases where the misaligned region contained less critical bitmap or texture data, the corruption went unnoticed until it manifested as intermittent screen glitches. This explains why Torvalds observed both predictable kernel job timeouts and occasional random screen corruption in the wild.
The two-year gap between the introduction of the bug and its becoming reliably reproducible suggests the issue was always latent, but user space behavior changes (such as different memory allocation patterns or GPU usage profiles) finally triggered consistent exposure of the flaw, allowing Torvalds to reproduce it reliably and fix it.
Pick your industry and the AI tools you use, and get news related to your work every day.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.
Reflection AI introduced Beam, an open-weight model for agentic coding and long-horizon tasks, with 501 billio…

The walkthrough points the CLI at a local mock via the ANTHROPIC_BASE_URL environment variable

A developer released agent-guardrails, a one-script Python standard-library plugin that guards Bash, Write, Ed…

A non-engineer operator says one person ships four smartphone apps on Google Play, three on the App Store, wit…

A Zenn guide explains systems to install before letting AI agents, bots or scheduled jobs post, send, publish…

Researchers at Microsoft published a paper titled "Adoption and Impact of Command-Line AI Coding Agents: A Stu…
