What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
As of October 7, 2026, the reviewed announcements confirm that Linux 7.3 was still in release-candidate testing: Linux 7.3-rc1 was announced on August 30 and rc4 on September 20. They do not verify a stable release. The cycle has a large initial change set and previewed removals of some legacy support, but neither fact alone shows that the kernel is unusually unstable or that most users will be affected.
What does “off course” mean for Linux 7.3?
Linux 7.3 here means the upstream Linux kernel series, not Red Hat Enterprise Linux 7.3 or a distribution release. A kernel release can encounter problems as developers stabilize a broad set of changes, or when a change exposes a compatibility issue for a particular device, driver, filesystem, or workload. The available release announcements describe development activity; they do not establish a broad regression or give a universal measure of release safety.
As an Amazon Associate I earn from qualifying purchases.
Release candidates are part of the testing and stabilization process, not the stable release itself. Linus Torvalds announced rc1 after the merge window closed on August 30, then described rc4 activity on September 20. An August preview anticipated a late-October release, but that was an estimate, not a confirmed date. Torvalds’s rc1 announcement; his rc4 announcement; Phoronix’s August preview.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWhy was the Linux 7.3-rc1 change set so large?
Torvalds called rc1 large, noting that it was among the bigger releases by commit count, but also gave a specific explanation: about a third of the patch was AMD DCN6 GPU register headers and related code. He said that discounting this block, the rest of the merge window looked fairly normal. That approximate share describes the patch, not the fraction of new features, risk, or regressions.
#1 Best Overall
So the headline-sized diff is a reason to look at what changed, not proof that 7.3 is in trouble. The explanation and qualification come from Torvalds’s August 30 rc1 announcement.
What could affect particular users?
Previewed removals of legacy support
Phoronix’s August 14 preview listed planned removal of old SGI and serial-card drivers, FreeVxFS, and EFS. The preview establishes that these removals were proposed for the cycle; it does not, by itself, confirm that every item remained in the final stable kernel. Users whose systems depend on one of those specific drivers or filesystems are the people most likely to care. The list is not evidence that ordinary desktop systems broadly lose hardware or filesystem support.
If you rely on a legacy component, check the final 7.3 release notes and your distribution’s kernel documentation before changing kernels. The preview is available from Phoronix.
Changes across active subsystems
The cycle also included substantial proposed work across subsystems. A sched_ext maintainer pull request described completing enqueue-path support for hierarchical sub-scheduling, while a networking pull request covered a broad range of changes. These pull requests document submitted work; they are not proof that every patch landed unchanged in the stable kernel. See the sched_ext pull request and the networking pull request.
Rank #3
What did the later release-candidate update indicate?
In the rc4 announcement on September 20, Torvalds described the patches as mostly small and spread across drivers, filesystems, networking, architecture fixes, and tooling. Filesystem work was a noticeable part of the activity. This is a progress report, not a guarantee that no bugs remain; it does, however, provide no evidence in itself of a cycle derailed by a single widespread failure. Read the rc4 announcement.
Do broader Linux kernel CVE reports mean 7.3 is less safe?
No such conclusion follows from the cited coverage. A September 1 Tom’s Hardware report discussed kernel-wide CVE findings and maintainer workload; it did not establish a Linux 7.3-specific vulnerability count or show that this release is less safe. General reporting about vulnerabilities across the kernel should not be relabeled as a tally of flaws in 7.3. Tom’s Hardware’s report.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Should you move to Linux 7.3?
There is no evidence here to support a blanket upgrade recommendation. The right choice depends on your distribution’s packaging and support policy, your hardware and workload, whether you need a change in the new kernel, and how much you value a kernel your distribution has already tested.
Quick Recap
Best Value
- Check the distribution first: upstream kernel release status and the kernel offered by a distribution are not the same thing. Use your distribution’s release notes and support guidance for its package.
- Check legacy dependencies: if your system relies on a driver or filesystem named in the preview, confirm its status in the final kernel and distribution documentation before switching.
- Match the kernel to your use case: new hardware or subsystem changes may matter to some users; those who do not need them may prefer their distribution’s established kernel and update process.
- Follow your normal recovery practice: keep a known-working kernel available where your distribution supports that option, and test a change against the hardware and workloads you depend on.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
