Remix.run Logo
▲ swinglock 3 hours ago

How are Ubuntu and RHEL not fixed? Few operating systems market themselves more as suitable for servers. What are they doing over there?

▲kev009 an hour ago | parent | next [-]

If you read commit logs of, say kernel.org and a distro kernel, and aren't concerned you are blissfully ignorant (and it is worse for the broader userland repos). It's particularly bad when they don't track a kernel.org LTS. Their kernel orgs are pretty lean and this has been the status quo for decades. CVEs of sufficient stature like this will get fixed but majority of other issues slip by unnoticed. LTS is kind of a myth, it trades ABI and API stability for a lot of other issues.

▲icedchai 16 minutes ago | parent [-]

Over the past few months I've started to install newer ubuntu kernels using the mainline PPA. However, it goes long periods of time without getting updates, so it's not really a satisfactory solution. In one case I just built the kernel myself.

LTS doesn't work if you want immediate fixes like the current environment requires.

▲gadtfly an hour ago | parent | prev | next [-]

Given the current and rapidly upcoming environment, would that not imply that those are no longer viable choices? As like a fairly urgent emergency consideration?

If they cannot demonstate being systematically able to adapt towards the required reaction time (minutes? hours?) by almost-comically many orders of magnitude (multiple weeks), and it is only going to get worse, then what other conclusion could there be?

Like they'll only organizationally adapt when it's far too late (everybody using their shit has already been pwned), and then it'll be an unpracticed emergency adaptation.

▲throw0101d an hour ago | parent | prev | next [-]

> How are Ubuntu and RHEL not fixed?

Ubuntu has had kernels in the "proposed" component for several days now if you want to pull it in manually. Not yet pushed to "security" or "updates".

▲1over137 8 minutes ago | parent [-]

Is there an RTFM for 'pull it manually'?

▲Shank 3 hours ago | parent | prev | next [-]

I’m pretty confused because apparently Anthropic is the group that followed “responsible disclosure” but apparently even though upstream was patched a couple weeks ago, still nothing on either.

▲Flockster 2 hours ago | parent | prev | next [-]

Going by the proxmox forum the fix is already in the sources (proxmox released their kernel based on them a few days ago). But I could not see, if it is already released for the users.

https://forum.proxmox.com/threads/cve-2026-98432-in-proxmox-...

▲tlamponi 2 hours ago | parent [-]

Yes, we (Proxmox) included the fix for this in 7.0.14-25, which was initially packaged two weeks ago.

It went through internal QA and to the test soon after that, then a few days later to the no-subscription repository and as of yesterday morning CET it was cleared for the enterprise one, so it's available on all repos of all Products we got in their current supported releases.

For kernel updates we where even more conservative in the past, but with the current churn on often quite relevant fixes picked up the pace a bit on moving them along, trying still to balance rolling out fixes fast(er) while not doing that so fast that tricky (hardware/setup specific) regressions don't get caught.

edit: As this makes the rounds we also released a PSA for it now [0] to make our status here easier to find.

[0]: https://forum.proxmox.com/threads/proxmox-virtual-environmen...

▲ an hour ago | parent | prev | next [-]
[deleted]
▲lakeviewterrace 2 hours ago | parent | prev [-]

Running regression tests I assume; they can't just YOLO shit like most OSS projects for the exact reason you mention.

▲1over137 3 minutes ago | parent | next [-]

It could be that it is more YOLO not patching this ASAP. Maybe better to risk some regressions.

▲swinglock 2 hours ago | parent | prev [-]

For a month?