Skip to content
senn-techsenn-tech
Back to blog
Infrastructure
Servers, Proxmox and network2026-11-20· By Franz Senn

Proxmox 9: the opt-in kernel 7.3 comes from a different source than before

Proxmox published a kernel 7.3 for Proxmox VE 9 in its own forum on 18 November 2026. The version number is the smaller news. What matters more is what it is built from: 7.3 is made directly on the upstream-stable branch of kernel.org, while the kernels of the earlier lines sit on top of the Ubuntu kernel. We checked this against our six hypervisor nodes and found a gap in our own view of updates.

Logo of Proxmox
Proxmox ships the 7.3 kernel as an opt-in in the test and no-subscription branches of Proxmox VE 9. (Quelle: Simple Icons (CC0), trademark: Proxmox Server Solutions)

The opt-in kernel 7.3 for Proxmox VE 9 is, according to Proxmox, its first kernel based directly on the upstream-stable branch of kernel.org instead of the Ubuntu kernel. It has been in the test and no-subscription branches of the Trixie-based releases since 18 November 2026. The 7.0 kernel stays the default, and Proxmox recommends production systems either stay on 7.0 or test 7.3 thoroughly on comparable hardware first.

What Proxmox changed at the source

From the announcement by Proxmox staff member t.lamprecht in the forum: the 7.3 kernel was uploaded to the test and no-subscription branches of every Trixie-based release, it stays an opt-in there, and the 7.0 kernel remains the default. Where earlier kernels were based on the Ubuntu kernel, Proxmox builds 7.3 directly on the upstream-stable branch. The stated reason is a shorter path in both directions: upstream fixes reach the kernel with less effort, and what Proxmox and its users find and fix applies directly to the code upstream maintains. The 7.3 kernel will not be made available for older release series.

The changelog in the Proxmox git tree shows the earlier way of building. For the newest build 7.0.14-30 of 16 November 2026 it reads:

* update sources to Ubuntu-7.0.0-44.44 plus the upstream stable changes up
  to v7.3.3 and v6.18.62 that Ubuntu prepared for its next update, bringing
  fixes for about 130 published security issues.
Two paths of an upstream fix into the Proxmox kernelkernel.org stablewhere the fix originatesUbuntu kernel tree7.0 line only: Ubuntuprepares the changesProxmox build7.0.14-xdefault in VE 9Proxmox build7.3.x-pveopt-in: straight fromkernel.org stable, no Ubuntustep
The first three steps describe the 7.0 line, the last step comes straight from kernel.org. Based on the Proxmox forum announcement and changelog. (Quelle: Proxmox forum and changelog)

So the 7.0-line kernel is an Ubuntu kernel with Proxmox patches, and fixes arrive on Ubuntu's schedule. With 7.3 that intermediate tree is gone. Three consequences matter for operations:

  1. Fixes follow the upstream cadence of kernel.org instead of Ubuntu's, which by Proxmox's own reasoning is the shorter path.
  2. Configuration and patch list differ from the Ubuntu builds. Proxmox itself calls this "a somewhat different regression risk", for example when an Ubuntu patch or a build option is missing. Anyone who builds DKMS modules, in our case a storage driver and the Mellanox MFT module, has to build them against the new kernel before a node boots from it.
  3. The end of the line depends on upstream. Proxmox considers 7.3 likely to become this year's upstream longterm kernel. kernel.org does not confirm that yet: on 20 November 2026 it lists 7.3 as stable, with no longterm designation.

The version number does not say which fixes are inside

All six of our nodes run build 7.0.14-26 of 22 October 2026. Its changelog entry has no source line; that line sits in the preceding build -25:

proxmox-kernel-7.0 (7.0.14-25) trixie
  * update sources to Ubuntu-7.0.0-43.43i1, based on the upstream stable
    releases up to v7.2.9 and v6.18.55 and carrying many additional security
    fixes.

From -25 on, the line therefore carries upstream changes up to v7.2.9 and v6.18.55 according to the changelog, including fixes from lines above its own version number. The 7.0.14 names the base, and the contents are in the changelog. Proxmox publishes no CVE-to-build table; the information exists only in the changelog entries.

The gap between our build and what Proxmox builds for the same line has grown. Changelog dates of the recent builds, days to 20 November 2026:

BuildChangelog dateDays to 20 Nov
7.0.14-2024 Sep 202657
7.0.14-2517 Oct 202634
7.0.14-26 (installed on our nodes)22 Oct 202629
7.0.14-2731 Oct 202620
7.0.14-2802 Nov 202618
7.0.14-2906 Nov 202614
7.0.14-3016 Nov 20264

Source: changelog of the Proxmox kernel package, retrieved 20 November 2026. Between -20 and -30 there are ten builds in 53 days, one roughly every five days.

The 7.0 line at kernel.org saw its last tarball in June

The tarball listing at kernel.org shows only files that exist. As of 20 November 2026:

LineTarballsLast tarballDateDays to 20 Nov
7.0157.0.1427 Jun 2026146
7.1147.1.1302 Sep 202679
7.2167.2.1501 Nov 202619
7.367.3.517 Nov 20263

As a control, linux-7.0.15.tar.xz answers 404 and linux-7.3.5.tar.xz answers 200. The kernel.org/releases.json list shows only 7.3.5 as stable and 7.2.15 as end-of-life on the same day; 7.0 and 7.1 no longer appear in it. The 7.0 line has had no upstream tarball since the end of June, and 7.2 has ended as well.

Days since the last upstream tarball per 7.x line, measured 20 Nov 20267.0146 · 146 days, last 7.0.147.179 · 79 days, last 7.1.137.219 · 19 days, last 7.2.157.33 · 3 days, last 7.3.50160
Derived from the dates in the kernel.org tarball listing, retrieved 20 November 2026. Each bar is one kernel line. (source: kernel.org, directory listing v7.x)

For our line there is nothing left to collect at kernel.org after 27 June 2026. What keeps coming are Proxmox's own builds, which according to the changelog carry upstream changes from the tree Ubuntu prepares. The 7.3 branch removes that intermediate step.

The freeze effect: updates that apt no longer lists as updates

Our nodes hold back kernel, headers, firmware and one DKMS module in two ways. The first is a file in /etc/apt/preferences.d:

/etc/apt/preferences.d/99-freeze
Package: proxmox-kernel* proxmox-headers* pve-firmware kernel-mft-dkms
Pin: release *
Pin-Priority: -1

The second is dpkg holds. On one of the nodes we measured, 50 packages are on hold, 21 of them kernel, header and firmware packages. Both are active here at the same time, with different effects: according to the apt_preferences manual page a negative priority prevents the version from being installed, while a hold only marks the package as held back. Measured on one node:

# apt-cache policy proxmox-kernel-7.0.14-29-pve-signed
proxmox-kernel-7.0.14-29-pve-signed:
  Installed: (none)
  Candidate: (none)
  Version table:
     7.0.14-29 -1
        500 https://enterprise.proxmox.com/debian/pve trixie/pve-enterprise amd64 Packages

The package is in the index, its priority is -1, and there is no candidate. For any check that runs over the update list that means:

# apt list --upgradable | grep -c kernel
0

Twelve packages are on that list, among them Corosync, pve-qemu-kvm and qemu-server. Not one of them is a kernel. apt-get -s upgrade ends the same way with "0 upgraded … 12 not upgraded". Anyone who reads the 12 as the whole backlog never sees the kernels, because the 21 held kernel, header and firmware packages are not in that number. A watcher that counts the length of this list reports six quiet nodes.

Our rule from that: kernel state comes from apt-cache policy and the package index, not from the upgradable list. The list shows only what apt is willing to touch.

Where our six hypervisors stand

Own measurement on 20 November 2026 on six Proxmox VE 9 nodes (Trixie, enterprise repository), with uname -r, apt-cache policy and apt list --upgradable; the index state is the nightly apt update run of 18 November 2026. All six nodes show the same picture:

MeasurementValue on all 6 nodesMeasured with
Running kernel7.0.14-26-pveuname -r, 20 Nov 2026
Newest build in the index7.0.14-29apt-cache policy, index of 18 Nov 2026
7.3 packages in the index0apt-cache policy, index of 18 Nov 2026
Upgradable packages12, of which 0 kernelapt list --upgradable, 20 Nov 2026

Three builds from 31 Oct, 02 Nov and 06 Nov are missing on our nodes; the newest build in the index was 14 days old on the measurement day, and build -30 of 16 Nov was not in the index yet. "Opt-in" read literally means: not a single 7.3 package sits in the index our nodes use, the Trixie enterprise branch. According to Proxmox the 7.3 packages are in test and no-subscription, which our nodes do not use.

Staying on 7.0 therefore does not cost nothing. kernel.org delivers nothing more on that line, but the gap to Proxmox's own builds keeps growing, and those builds are where the fixes are.

The freeze stays deliberate. The nodes run DKMS modules for storage and network tooling. A kernel change means rebuilding those modules and rebooting the nodes inside the HA cluster. Both can be planned and both need a window.

What moving to 7.3 would mean for us

For our environment the 7.3 branch is a decision about the source, with three conditions:

  • Rebuild the DKMS modules against the 7.3 build and boot one node the HA cluster can spare, including storage IO under load.
  • Tie the move to the state of the 7.0 builds in your own repository. A node that is four builds short of -30 has no case yet for switching the source.
  • Plan the same check for the new line: which upstream version sits in which build is written down only in the changelog, and that changelog will look different for 7.3.

From the forum feedback, one report: a user writes that Proxmox Backup Server backups on his machines were clearly faster under 7.3 than under the last 7.0 builds, and offers no explanation. That is anecdote, not a measurement. The announcement itself lists no known issues at the time of writing.

Checks for your own environment

  1. Measure the running kernel and the offered builds separately: uname -r for the running system, grep over the index files in /var/lib/apt/lists for what is offered. The upgradable list serves for neither.
  2. Keep track of how kernel packages are held back: cat /etc/apt/preferences.d/* and dpkg --get-selections | grep hold. Two mechanisms, two visibilities, and both can be active at once.
  3. Record the index date with every index number: an index from the 18th says nothing about builds published later.
  4. For your running line, look up the last upstream tarball at kernel.org. No new tarball for weeks means the vendor does the maintenance, and a CVE then reaches a build through that vendor's changelog.
  5. Before an opt-in switch, build the DKMS modules against the new kernel and test the boot path on a node you can spare.
  6. Change the watchers: the count of offered kernel packages becomes its own measurement next to the count of upgradable packages.

Without holds, 7.3 is a normal update in the test branch. With holds, first check whether the list you rely on shows kernels at all. On our six nodes it did not.

How we otherwise check kernel advisories against our own fleet is in CVE-2026-98432: how we re-measured the TCP kernel flaw on four Ubuntu servers. Why a single host can stall a whole patch round is covered in Patch round: one host stops the fleet. More measurements on hypervisor and server operations are collected in the topic area Servers and network. To have the kernel state and update visibility of your Proxmox nodes checked, see IT operations and infrastructure for where we start.

Further sources

Retrieved on 20 November 2026 in each case, primary sources first.

Own measurement: six Proxmox VE 9 nodes (enterprise repository, Trixie, kernel 7.0.14-26-pve), commands uname -r, apt-cache policy, apt list --upgradable, apt-get -s upgrade and dpkg --get-selections, measured on 20 November 2026, index state 18 November 2026; raw output is not published.

Questions?
Do I have to move to the 7.3 kernel on Proxmox VE 9 now?+

No. The 7.3 kernel sits in the test and no-subscription branches of the Trixie-based releases and stays an opt-in there, while 7.0 remains the default. Proxmox recommends staying on 7.0 for production systems, or testing thoroughly on comparable hardware first. If you also pin kernel and firmware through apt, the new package changes nothing for you at first.

Why does apt list --upgradable show no new kernel when the repository holds newer builds?+

An entry in /etc/apt/preferences.d with Pin-Priority -1 removes the package from apt's selection. apt-cache policy then reports Candidate: (none) even though the version is in the index, and the list of upgradable packages has no line for it. Only apt-cache policy and the package index show the kernel state.

Is a 7.0.14 kernel unsafe because kernel.org no longer publishes tarballs for the 7.0 line?+

Not automatically. The version number names the base. What a build contains is written by Proxmox into the changelog of the kernel package: build 7.0.14-25 carries upstream changes up to v7.2.9 according to that changelog. The number to measure is the gap between the installed build and the newest one your own repository delivers.