RepoJournal
Linux

Linux

The kernel, distros, and the rigs of the moment

Pick a date

  1. Sun 3 may
  2. Mon 4 may
  3. Tue 5 may
  4. Wed 6 may
  5. Thu 7 may
  6. Fri 8 may
  7. Sat 9 may
  8. Sun 10 may
  9. Mon 11 may
  10. Tue 12 may
  11. Wed 13 may
  12. Thu 14 may
  13. Fri 15 may
  14. Sat 16 may
  15. Sun 17 may
  16. Tue 19 may
  17. Wed 20 may
  18. Thu 21 may
  19. Sat 23 may
  20. Sun 24 may
  21. Mon 25 may
  22. Tue 26 may
  23. Wed 27 may
  24. Fri 29 may
  25. Sat 30 may
  26. Sun 31 may
  27. Mon 1 jun
  28. Mon 8 jun
  29. Tue 9 jun
  30. Today 10 jun

The Wire · Showcase

FUTEX BUG FIX CLOSES MEMORY CORRUPTION HOLE; DRM STACK STABILIZING

By RepoJournal · Filed · About Linux

The kernel just plugged a use-after-free in futex allocation that was corrupting shared memory contexts, while graphics drivers landed their heaviest rc2 patch set in weeks.

The futex fix [1] removes a strict CLONE_THREAD dependency that was causing KASAN slab-use-after-free panics when mm structures were shared outside pthread semantics. This was a real corruption bug — the kind that silently corrupts state before crashing — so any system doing non-standard process sharing gets relief here. Meanwhile, DRM merged its rc2 fixes [2] with the usual amdgpu/xe double-header after some maintainer access issues left xe backlogged. The graphics payload includes GFX12 debug config fixes, analog support restoration, and framebuffer geometry corrections that will matter for display stability. On the subsystem side, io_uring [3] fixed a recvmsg multishot bug where incrementally consumed buffers were throwing spurious -EFAULT, and s390 [4] rejected zero-length writes that were corrupting Debug Facility buffers. SPI drivers [5] got fixes in axiado and rockchip that Mark Brown flagged as nasty — worth auditing if you're running those controllers in production.

Action items

References

  1. [1] futex: Drop CLONE_THREAD requirement for private default hash alloc torvalds/linux
  2. [2] Merge tag 'drm-fixes-2026-05-02' of https://gitlab.freedesktop.org/drm/kernel torvalds/linux
  3. [3] Merge tag 'io_uring-7.1-20260430' of git://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux torvalds/linux
  4. [4] Merge tag 's390-7.1-2' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux torvalds/linux
  5. [5] Merge tag 'spi-fix-v7.1-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi torvalds/linux

FAQ

What changed in Linux on May 2, 2026?
The kernel just plugged a use-after-free in futex allocation that was corrupting shared memory contexts, while graphics drivers landed their heaviest rc2 patch set in weeks.
What should Linux teams do about it?
Pull futex fix immediately if you have workloads sharing mm structures across CLONE_THREAD boundaries • Test DRM stack if you ship rc2; amdgpu/xe fixes are substantial • Audit io_uring recvmsg multishot if you're consuming buffers incrementally
Which Linux repositories shipped on May 2, 2026?
torvalds/linux

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.