The 6.18.3 stable kernel rebase contains new features, enhanced hardware support, and a number of important fixes across the tree.
The 6.17.13 stable kernel updates contain a number of important fixes across the tree.
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2026-8ff894a3dfPlease log in to add feedback.
| 0 | 16 | Test Case kernel regression |
This update has been submitted for testing by jforbes.
This update's test gating status has been changed to 'waiting'.
This update has obsoleted kernel-6.17.13-300.fc43, and has inherited its bugs and notes.
default & performance tests pass (KVM)
Working fine here so far.
This update's test gating status has been changed to 'failed'.
All is working fine, tests passed
` AMD Ryzen 7 5700U with Radeon GraphicsWorks.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
Works for me, the default tests passed OK..
Work Station, Asus prime mobo - Ryzen5 5600g/iGPU, 400 Series Chipset, 32 GiB RAM. (UEFI) Secure boot, 2x SSD's > RAID1 (ext4)
Works fine on HP EliteBook x360 1040 G6.
Works well here. Ryzen 3700x, Rog Strix B550-F, Nvidia from rpmfusion.
Overall works great, but just FYI, there is a regression on AMD GPUs with VRR: https://gitlab.freedesktop.org/drm/amd/-/issues/4824, not the end of the world, but annoying for sure
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
Works
Works for me.
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=2407021 for me.
Working as expected on my Lenovo ThinkPad E14 Gen 4 (Intel).
Works
sudo akmods --force --rebuild [sudo] Mot de passe de xxxxx : Checking kmods exist for 6.18.3-200.fc43.x86_64 [ OK ] Building and installing acpi_call-kmod [ OK ] Building and installing nvidia-kmod [ OK ] Building and installing VirtualBox-kmod [ OK ]
6.18.3-200.fc43.x86_64incl.kernel-headers-6.18.3-200.fc43work fine in average day activities on AMD Ryzen 7 PRO 6850U. No external modules, kernel taint value = 0. F43 KDE with confined users.Seems to work fine on bare-metal Lenovo ThinkPad L390 with UEFI and SecureBoot. No issues to report so far and kernel regression tests PASS.
Tested on Fedora 43, GNOME Wayland, kernel 6.18.3-200.fc43. Hardware: Dell Thunderbolt Dock WD19TB (USB-C/Thunderbolt).
Previously observed USB issues (timeouts -108, hub suspend failures after suspend/resume) are no longer present.
USB-C/Thunderbolt disconnect and reconnect is now handled cleanly: – PCIe link down/up handled correctly – xHCI controller re-initialized – All dock devices (USB hub, keyboard, mouse, Ethernet r8152) are re-enumerated successfully
One USB port power cycle attempt was observed, but recovery succeeded and system remained stable.
Overall: stable, no regressions observed in daily use.
Works well on a Framework 13 with AMD Ryzen AI 300 Series CPU.
Works well. (Intel® Core™ i5-11400F + NVIDIA GeForce RTX 3060 Ti)
Lunar Lake audio is not working with this update: see https://bugzilla.redhat.com/show_bug.cgi?id=2415785
Works great! LGTM! =)
Works on R5600X + RX9070XT and Xeon W-2225 + Arc A380
Works on a whole bunch of aarch64 devices including RPis
Seems to be working fine on Ryzen 7 9700x with rx 9700
Working fine on AMD 7945HX + Radeon 610M. Finally fixed random display freezes that was introduced in later 6.17.* kernel releases
Works well on a AMD Ryzen 9 5900X + Radeon RX 6900 XT system.
This is still failing coreos tests, but I don't know if that should block this kernel update. The use case is a bit of a corner case. https://github.com/coreos/fedora-coreos-tracker/issues/2087
test suite performed
Works
AMD 5600G test was a PASS.
Works just fine for me on framework laptop and older stationary machine
Appears to work ok so far on a 6th Gen Lenovo P14s, a HP Z440 workstation. and a couple of AMD A9-9400 NUCs I have lying around.
More critically, it fixes a 6.17 regression observed with two different FTDI USB<>serial adapters.
Breaks ostree hot fix & sysexts. See: https://github.com/coreos/fedora-coreos-tracker/issues/2087 & FEDORA-2025-df28d79493
I installed this on my Fedora Linux 43 Red Hat CSB Remix system, which is a Lenovo ThinkPad X1 Carbon Gen12. I also have a recent Intel Meteor Lake-P chip and decided to try out the
xedrivers by editing my kernel boot parameters manually withi915.force_probe=!XXYY xe.force_probe=XXYY, whereXXYYis the PCI ID I got fromlspci -nnd ::03xx.I booted successfully into GNOME and things do feel a bit more smooth. I am running the 6.18 kernel, which I believe had a significant amount of
xeenablement work done, but I could be wrong.No issues noted after rolling out to my home network.
Workstation:
CPU: 13th Gen Intel(R) Core(TM) i5-13400F (16) @ 4.60 GHz Host: Z690 PG Velocita GPU: AMD Radeon RX 6600 [Discrete] OS: Fedora Linux 43 (Workstation Edition) x86_64 DE: GNOME 49.2 WM: Mutter (Wayland)
Server:
CPU: Intel(R) Xeon(R) E-2226G (6) @ 4.70 GHz Host: WS C246M PRO Series (4107) GPU: Intel UHD Graphics P630 @ 1.20 GHz [Integrated] OS: Fedora Linux 43 (Server Edition) x86_64
Pool of KVM VMs and podman containers
I have 3 Intel systems: in 2 of them 6.18.3 (fc43 ws) works fine. In an old HP Probook laptop with an Intel i5 3210M, 8GB RAM and SSD, Kernel-core 6.18.3 crashes on startup.
works fine with Thinkpad P1 Gen4
Regression report (Fedora 43, KDE Plasma Wayland)
Tested this kernel update and can confirm a regression compared to 6.17.x.
On kernel 6.18.x, plugging in an external HDMI monitor results in:
On kernel 6.17.12-300.fc43, the same hardware and setup work normally.
Journal logs on 6.18.x show:
This suggests a regression in the 6.18.x DRM / display hotplug path, possibly affecting KWin Wayland. Interested to know if others see similar behavior on this build.
HW is a Lenovo P1 Gen7 (im using integrated Intel ARC only)
I created a ticket at hopefully the right location: https://gitlab.freedesktop.org/freedesktop/freedesktop/-/issues/2904
This update has been submitted for stable by jforbes.
This update has been pushed to stable.
Why was the repeated negative feedback here ignored? https://bodhi.fedoraproject.org/updates/FEDORA-2026-8ff894a3df#comment-4503686
It was not, read the ticket about that. There has been active discussion for quite some time. https://github.com/coreos/fedora-coreos-tracker/issues/2087 And based on the feedback in that ticket, I am about to build 6.18.4 without a fix as well. I expect 6.18.5 next week will have the fix for that issue.