WTF Ubuntu?

16 days ago (chalmovsky.com)

Worse yet, the Ubuntu security incident page[0] lists "Ubuntu Priority: High" (as opposed to Critical, which would trigger an out-of-schedule patch). There's a "Why this priority?" link that simply says:

> Why is this CVE high priority?

> See ubuntu cvss score

That's it, we don't even get a period on this TBD of a sentence. It's followed by a generic link that explains what "Ubuntu Priority" is, but that page contradicts their choice. Note that it doesn't offer any mitigations either, and even the (horrendously unclear) description is copied from the NIST page, so there's no actual message from Ubuntu.

I already had a bad feeling the first time I saw "Get more security updates through Ubuntu Pro" on `apt upgrade`, this is now the kick I needed to move to a different distro.

[0] https://ubuntu.com/security/CVE-2026-98432#priority-reason

  • I don't think this is fair. They don't do a good job of pointing you at their rationale which is in their security score here[0]. I ultimately had to have claude translate the kernelese in to something my small brain could understand but this is a bug that could crash your system but is unlikely to expose your confidential system data to attackers or degrade data on the system. Especially given that the exploit can only be done if packets with IP options. IP options are commonly dropped or removed from packets on the open web. You not only need a vulnerable system but a vulnerable request path through the internet which you would only know by trying this attack which is very timing dependent with the SYN,Retransmitted SYN and Reset all happening very close together. A motivated attacker could probably do this on your network but over the internet ... It sounds unlikely.

    [0]https://ubuntu.com/security/CVE-2026-98432#impact-score

    • > this is a bug that could crash your system but is unlikely to expose your confidential system data to attackers or degrade data on the system

      Red Hat disagrees[0][1]. They might be parroting Anthropic, and Anthropic might be exagerating the impact (likely!), but that's the current consensus about the vulnerability. If Ubuntu disagrees, they should have said something and not pasted "Cvss 3 Severity Score 9.8 · Critical" at the top of the page.

      > A motivated attacker could probably do this on your network

      I find that's still catastrophic given how centralized cloud environments are.

      [0] https://access.redhat.com/security/cve/cve-2026-98432

      [1] https://access.redhat.com/security/vulnerabilities/RHSB-2026...

      3 replies →

    • Greg Kroah-Hartman the long-time Linux kernel maintainer (USB, PCI, driver core, sysfs, and -stable releases) gave a talk on LLM assisted CVE discoveries. In that talk, he downplayed those exposed CVEs from Mythos. What you described above matches his sentiment on downgrade those CVE vuln score.

      See previous discussion and the actual talk on YouTube:

      https://news.ycombinator.com/item?id=49929391

    • > but this is a bug that could crash your system but is unlikely to expose your confidential system data to attackers

      Given people have demonstrated getting root with it, unlikely seems questionable

      > Especially given that the exploit can only be done if packets with IP options. IP options are commonly dropped or removed from packets on the open web.

      It sounds like iphones use mptcp in the wild, which use tcp options, so im not sure how true this is.

      8 replies →

    • A problem, at least for me at work, is this has to be communicated to the people who make the decision around whether something can continue operating or has to be taken offline until fixed. So far, said people are not particularly interested in the details of CVEs, just if it's critical and has an exploit available. Which is fair I guess, they're absorbing the risk. I would like Canonical to go a bit faster which would make my life easier.

  • Yeah, their lack of a satisfactory response is the final nail in their coffin. This incident escalates my consulting advice about Ubuntu from “not recommended” to “switch immediately”.

    Some of my clients may be surprised by this change, as I once advocated for Ubuntu as a good choice for a development and deployment platform. While that has not been true for quite a while, they have now jumped the shark into eel-infested waters; I cannot take them seriously any longer.

  • The more I look at this the angrier I get. This is a CVE that Anthropic claims can get a Remote Code Execution on vulnerable systems, which includes default Ubuntu installs running any sort of Go server like Caddy. Bad enough that I shut down my personal website and self-hosted tools (sorry for any typos, my grammar checker is also down).

    And this is how Ubuntu describes the vulnerability to sysadmins:

      In the Linux kernel, the following vulnerability has been resolved:
      ipv4: free inet_opt and ireq_opt after an RCU grace period
      tcp_v4_syn_recv_sock() transfers ownership of ireq->ireq_opt to the
      child socket (newinet->inet_opt) without copying it.
      Another cpu can concurrently process a retransmitted SYN for the same
      request socket, and send a SYNACK from tcp_check_req().
      tcp_v4_send_synack() and inet_csk_route_req() read ireq->ireq_opt
      under rcu_read_lock() only, and ip_build_and_send_pkt() and
      ip_options_build() then read opt->optlen twice.
      Note that the SYNACK timer itself is not an issue: it holds a
      reference on its request socket, and inet_csk_reqsk_queue_drop()
      calls timer_delete_sync() before the child can be freed.
      Since commit 079096f103fa (“tcp/dccp: install syn_recv requests
      into ehash table”), request sockets are processed without holding
      the listener lock, so nothing prevents the child socket from being
      freed while the SYNACK is still being built. TCP child sockets do
      not have SOCK_RCU_FREE, and inet_sock_destruct() frees inet_opt
      with a plain kfree(), leading to a use-after-free in
      ip_options_build().
      A similar issue exists with request socket migration
      (net.ipv4.tcp_migrate_req=1, or a BPF_SK_REUSEPORT_SELECT_OR_MIGRATE
      program). reqsk_timer_handler() clones the request socket with
      inet_reqsk_clone(), so that the old request socket and its clone
      share the same ireq_opt, then reqsk_migrate_reset() clears the
      pointer in the old one. Another cpu holding a reference on the old
      request socket can still be using these options (sending a SYNACK,
      or creating a child in tcp_v4_syn_recv_sock()) when the clone is
      freed, and tcp_v4_reqsk_destructor() also uses a plain kfree().
      Readers already use RCU, and other paths replacing inet_opt
      (do_ip_setsockopt(), cipso_v4_sock_setattr()...) already use
      kfree_rcu(). Use kfree_rcu() in inet_sock_destruct() and
      tcp_v4_reqsk_destructor() as well.
      IPv6 is not affected by the first issue, because tcp_v6_syn_recv_sock()
      duplicates the options. tcp_v6_reqsk_destructor() has the same
      migration issue with ipv6_opt, which is only set by CALIPSO. This
      will be addressed in a separate patch.
    

    How is this in any way, shape, or form acceptable two weeks after the CVE was published?

    • sorry for any typos, my grammar checker is also down

      I assume this is unrelated to the Ubuntu situation, but how does a grammar checker go down? We've been doing offline grammar checking since computers had 64K of RAM.

      12 replies →

    • > running any sort of Go server like Caddy

      It's so much worse than this, and there is a staggering amount of misinformation running rampant about this bug.

      MPTCP is not a requirement, it can be exploited merely by sending specially crafted TCP packets with (any) IP options set. No special MPTCP support, web servers or any specific software listeners are even necessary at all to trigger it, just send the packets and boom.

      I think the reason people assume MPTCP is a requirement is because that's what the PoC used... but MPTCP itself also doesn't even rely solely on IP options.

      Ubuntu also does not even list a single mitigation strategy... at least RHEL did.

      And like I said, any normal TCP packet that contains IP (not TCP) options can trigger the bug. I cannot emphasize enough how important and absolutely ridiculous this is.

      Like the post says, this is big enough to get a massive amount of people to completely stop trusting Ubuntu entirely and jump ship.

      5 replies →

  • Moved to Debian few years back and never looked back. We used Ubuntu for a bunch of clients and unfortunately had to let them know they will have to migrate to Debian or similar. It's such a shame because I really used to love Ubuntu until Canonical started turning slowly into your typical everyday corporate.

  • As far as I know the only working exploit is working on machine with MultiTCP enabled. Redhat also downgraded the issue to "high" and also did not release a patch yet. I would have preferred a patch but I accept that they know better than me what they are doing.

    • Why would they take so long anyway and be behind volunteer run projects like debian? Is it something about corporate shenanigans and testing? because afaik in fedora for example firefox is always behind in security updates compared to debian.

      1 reply →

    • RHEL did release a new kernel. Presumably it has the fix (though I guess I didn't actually check)

  • They're totally asleep at the wheel, it's malpractice. The pitch for RHEL is highly competent maintenance you can't get elsewhere

    • RHEL also dropped a ball on it so yeah the alternative for paying for RHEL license is apparently "just use Debian or hire some Arch nerds"

  • > I already had a bad feeling the first time I saw "Get more security updates through Ubuntu Pro" on `apt upgrade`

    To be clear, Ubuntu Pro doesn't have the fix yet either, in case anyone's confused.

    • This was an old gripe unrelated to today's issue. But your clarification is exactly why it left a bad feeling back then, the message certainly implies that my system is not getting all the security updates it could get.

  • I believe RHEL/Alma/Rocky has released patches today. I have a notice about they have done so.

    • Alma released a patch ahead of upstream again, just like they did for several other critical vulnerabilities this year.

For the record, the kernels with the fixes are in the "proposed" repos for each LTS release:

* https://launchpad.net/ubuntu/+source/linux

You can pull them down with a "-t" added to your apt-get (but will not appear by default).

26LTS had the new kernel go to the updates/security repos on October 28.

  • > You can pull them down with a "-t" added to your apt-get (but will not appear by default).

    How does that look like exactly?

    • Edit /etc/apt/sources.list.d/ubuntu.sources to include resolute-proposed:

      Suites: resolute resolute-updates resolute-backports resolute-proposed

      Then update:

      sudo apt update -t resolute-proposed sudo apt install linux -t resolute-proposed

    • A friendly reminder that it's either "What does that look like, exactly?" or "How does that look, exactly?" - "how" and "like" don't go together.

      As for the way to add it, the full approach should be `add-apt-repository -yp proposed`, then `apt update`, then `apt install -t resolute-proposed linux-generic`

      2 replies →

  • It has severe regressions like https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/...

    • Updated and rebooted an LTS server today. It was a disaster.

      Kubernetes node went to pieces. Apparmor prevented nginx from doing anything sensible, so the ingress didn't work. Easy fix when you know what's up, not so apparent when starting troubleshooting.

      One app invoked tshark in a pod, apparmor denied it.

      Those two were the visible ones. Apparmor now also blocks some unix signals that e.g. postgres uses in a few circumstances - leaving latent annoying bugs.

      Pod shutdown hangs. Logs indicate 7 more apps affected by the signal "armor".

      We're banning any new Ubuntu installs.

      1 reply →

  • Your comment should be higher. Most indignant comments here are variants of "Tell me you don't know about CVE triage and Linux kernel releases without telling me you don't know about them". I mean, I also don't know a lot about them, but Canonical's security record has been exemplary in my experience, and I see no solid reason to doubt their process in this instance.

    First, if this CVE did truly put every Ubuntu machine on the Internet at risk, we'd know about mass compromises by now, and there haven't been any reports. It means the CVE is not trivially exploited.

    Second, the gravity of the CVE dictates the security release cycle. Emergency kernel patches carry risks of their own, and it would be worse to hurry a non-critical patch and crash a part of their massive user base.

    Edit: I've been enjoying this comment going up and then into the negatives, what a roller coaster.

    • You suggest that Canonical has concluded that this issue is not so bad and so it is Ok that they have not released a fix.

      Customers and users expect alacrity for CVSS 9.8 CVEs in un-hardenable services like the TCP stack.

      Whatever Canonical's security record or process has been for other CVEs does not excuse silence and delay in this case. Canonical, unfortunately, does not get to silently decide such a categorized CVE "is not trivially exploited" without criticism, and likely consequences.

      3 replies →

    • > Your comment should be higher. Most indignant comments here are variants of "Tell me you don't know about CVE triage and Linux kernel releases without telling me you don't know about them".

      Ubuntu managed to release the updated 26LTS kernel on October 28, but the other LTSes have been sitting around since 26 or 28, so I'm wondering why they haven't been moved to "security" or "updates" in the several days since.

      Especially since their page on it mentions October 15

      * https://ubuntu.com/security/CVE-2026-98432

      and Debian released a couple of weeks ago.

  • I'm not seeing CVE-2026-98432 included in the changelog for any of the new kernels on the 28th.

    • > I'm not seeing CVE-2026-98432 included in the changelog for any of the new kernels on the 28th.

      The versions are mentioned in this page:

      * https://ubuntu.com/security/CVE-2026-98432

      I'm wondering if the CVE in question is not mentioned because it was embargoed so they did not want to accidentally leak things while the kernel went through the (public?) QA workflow. Perhaps the Changelog will be amended at some point to have the CVE?

It’s okay to have criticism, but at least be constructive about it. This “I demand to speak to the manager” energy should be kept out of open source.

The post gives no details about what this vulnerability is, how critical it is, how it is impacting them personally, how vulnerable their servers are, how they are working around it.

Just a title designed to generate the maximum outrage followed by a few meaningless lines.

  • > The post gives no details about what this vulnerability is, how critical it is, how it is impacting them personally, how vulnerable their servers are, how they are working around it.

    Yes it does? And Ubuntu is selling security subscriptions and doing a poor job of it, These aren't open source volunteers, this is a paid product.

    • I read the whole post and still don’t have any idea what it is and how severe it is. Ubuntu has not marked it critical. Is there any reason to disagree with that assessment? In an entire post criticizing Ubuntu you’d think they would at least make that case.

      They have also not shared why they didn’t patch their kernel directly when updated versions have been available for a couple weeks now. Why wait for Ubuntu at all?

      9 replies →

    • You are talking about the company side of the issues. We are talking about the specific issue that is concerning our ubuntu servers. What is the security bug, and how can someone exploit it? Where is that written?

    • I'm not following, I don't believe a kernel patch like this would be limited to security subscribers. Or is your complaint that there's a security subscription program but no patch has been produced yet?

  • But Ubuntu is not some small distro maintained by unpaid volunteers; they are a corporation that offers paid support. I think it reasonable to be disconcerted when a company that you are paying for security updates is this negligent, especially when other distros have fixed this issue far more expediently.

    • I would expect paying customer to demand a dicount or their money back, but freeloaders get freeloader service.

      They have kernels out you can install if you really need them, they're just not merged into production repos yet.

      1 reply →

  • This is a major failure on Ubuntus part. The constructive feedback they deserve is literally the title of the article.

    The post gives enough detail, there is a vulnerability that allows root access on servers on the TCP stack, so literally accessible if you are running any service. There are exploits in the wild. Debian has the patched kernel, Ubuntu does not 2 weeks after the CVE is known.

    > how critical it is,

    9.8 out of 10 btw.

    > how it is impacting them personally,

    They are clearly rather upset by the lack of an appropriate response.

    > how vulnerable their servers are,

    They are literally open to anyone with an AI subscription.

    > how they are working around it.

    They are migrating off Ubuntu.

    • If Ubuntu offers LTS and is catering to business it is very much open to criticism. They can take it or leave it, but anyone is entitled to an opinion about it.

  • It's a large international corporation with hundreds of millions in revenue from enterprise contracts. There is in fact a manager to speak to and I do in fact demand to speak to them.

  • > It’s okay to have criticism, but at least be constructive about it.

    Nah, if you're dropping the ball after you said you wouldn't and I trusted that, I'm going to get angry and loud when you drop the ball. That's just reality, and Ubuntu isn't some Johnny-come-lately volunteer organization. They're one of the most well-funded Linux organizations in the world.

  • With Open Source / Free Software we're trying an alternate economic model, shooting to overtake the standard model. We rely on volunteers. It creates an awkward situation where we can't be unappreciative of effort (no matter the quality of output), but we also have to have expectations or this model is just not going to work.

    So we should respectfully expect better than this. (With the caveat that Canonical is a business. I'm using Ubuntu Pro for free so I won't be berating them, but I think I paying customers perhaps should be.)

    I also think that we should consider a sort of an "SLA" concept. If you say "I got you covered" and you drop the ball, I think I do have a grievance in that I could have chosen another option, and now I have to take the time to adjust. On the other hand sometimes people don't actually say "I got you covered" they say "This is a cool thing I'm working on". So something like an "SLA" could clear that up.

  • > at least be constructive about it

    I think the proposed solution here is pretty clear. Patch the bug.

  • > The post gives no details about what this vulnerability is

    It is a very famous vulnerability that has been all over tech news sites. Sometimes it is ok to assume the audience has the slightest bit of background knowledge about the topic at hand.

  • >The post gives no details about what this vulnerability is, how critical it is

    what? the literal first paragraph says:

    "In case you missed it: CVE-2026-98432 is a critical (CVSS 9.8) bug in the Linux kernel's TCP code. It's been there since 2016, so virtually every Linux server on the planet has it, and it can be hit remotely"

  • I believe you will have a ton of factual page about that. The purpose of this one is exactly what you criticise: rage. With a small error of margin a justified rage. I believe this was the reason it was chosen for submission: to show the rage.

  • The whole point of paying for Ubuntu enterprise services is you don't have to worry about all this nonsense. It's one thing if you're using Ubuntu for free, it's another thing when you're paying them for a specific service.

  • > This “I demand to speak to the manager” energy should be kept out of open source.

    This. You are welcome to publish patches and demonstrate how people can fix their own machines out of band with what Ubuntu does. This costs you... 10 minutes with AI help?

    While it's easier than ever to complain this year, I'm patching all the things while on a walk or not at my computer, it's great!

    Welcome to the world of tomorrow

To be fair: while critical (9.8) it has an EPSS score of <1% (probability of it being actually used). According to [1], [2], and others, at worst the issue results in a kernel crash or a denial of service. I read the post by Anthropic too, but something just doesn't reconcile there between everyone saying its a DoS, and Anthropic alone claiming RCE. So far the advisories I read state "under specific conditions ... result in a kernel crash" and similar.

[1] https://app.opencve.io/cve/CVE-2026-98432 [2] https://aws.amazon.com/security/security-bulletins/2026-160-...

  • As the days pass the probability of it being actually used is increasing. The EPSS score is clearly just an estimate, and according to the nist cve database, attack complexity is low so I would take the EPSS score with a grain of salt.

  • I had the same question about the actual exploit on another thread: https://news.ycombinator.com/item?id=50319143

    It’s only recently I realised that a lot of these very clever vulnerabilities are often not actually exploitable, except in quite specific conditions.

    • Something like this is rowhammer. Can it be exploited in a lab setting vs practically in the wild? Is fail2ban + WAF sufficient? How much network traffic is needed to remotely trigger the exploit in the field? How much inside knowledge of the system itself needs to be known?

      These go from extreme edge cases to viable approaches over time, so it needs to be patched. I think the really messed up thing is the lack of communication from the Ubuntu team. If they have a rationale either way, that's fine. They may disagree on the severity, identified a problem in the fix, etc, but the lack of transparency is causing a loss of confidence in the team's abilities.

I knew what this is about before clicking the link. While trying to find remediations for vulnerable systems I was also looking for any kind of "official" statement on literally WTF is going on here from the Ubuntu side, but I haven't been able to find one yet. I guess it has to go through the "hacker news puts enough attention on it for someone to care" phase which we all know so well...

  • If you had to manage what has become critical infrastructure around the globe using something like Launchpad, you'd understand.

    It's not optional.

Hi all, representing Canonical's product team here. We have fixes available for Ubuntu 22.04 LTS and newer in the -proposed pocket which are being tested for stability. These can be applied by users and we published a blog with the details. We sincerely appreciate the feedback and will follow up as soon as we can with more information https://ubuntu.com/blog/fixes-available-in-proposed-pocket-f....

  • This really needs to be hot fixed and just fast tracked to release. It’s for sure costing Canonical’s image and makes it difficult to continue to consider Ubuntu for serious server deployments going forward.

  • The fix is available in the -proposed pocket for users who perform their own kernel acceptance tests. Under our unified two-week kernel SRU cycle, in the first week we build and smoke-test kernels and publish them to -proposed. In the second week we run certification and regression tests on Ubuntu Certified hardware. Once that testing completes, the kernels are released to the -updates and -security pockets. We keep this step to avoid regressions, and we think it’s the right balance between speed and reliability.

    • IMO Three weeks is not a right balance of anything. I don't blame you personally, but taking this long is completely unacceptable. These issues are going to keep happening even more frequently as time goes on, so something needs to change. Your customers are going to start blaming you (even legally) for their systems getting hacked due to your company's negligence.

      I will not be using Ubuntu for any future desktops, laptops, servers, containers or anything else.

  • Why are the relevant packages not available in the main or even security repos?

    Three weeks is plenty of time.

Have companies been compromised because of this vulnerability? Ubuntu has an absolutely massive install base. The lack of notable incidents suggests that 9.8 might not reflect real-world well.

Maybe it's time for StealMyBitcoinV2…

Here is Ubuntu’s webpage on this vulnerability:

https://ubuntu.com/security/CVE-2026-98432

It’s still, over a week after disclosure and patches, unpatched in Ubuntu.

As for me, a part of me wants to move over to Rocky Linux 10.

I get the frustration, but isn't there an iptables rule that is a viable mitigation? Why not deploy that first?

  • Because you shouldn't have to do mitigations for this level of severity while waiting weeks for OS patch. I did that, but now I'm waiting for patch to unwind my mitigations.

  • Why do you ask such simple and obvious questions!? :-P

    nft add table ip cve_2026_98432

    nft add chain ip cve_2026_98432 pre '{ type filter hook prerouting priority -300; }'

    nft add rule ip cve_2026_98432 pre meta l4proto tcp ip hdrlength gt 5 counter drop

" Anthropic says it built a working exploit that gets root on a server. A total takeover."

From the linked Ubuntu CVE page

" Vulnerable system - Confidentiality impact Low

Vulnerable system - Integrity impact Low

Vulnerable system - Availability impact High

" suggesting it's more of a denial of service. So which is it, there are dozens of kernel CVEs fixed in the linked debian email.

  • This is what I want more information on, especially before we start pitchforking ubuntu or whoever

All the people working at Canonical have gone through the Canonical hiring process, which is quite possibly the worst in the global industry and I can't imagine anyone competent getting through it.

What is keeping people on Ubuntu instead of just using Debian? I'm genuinely curious. What is Ubuntu offering that Debian doesn't provide?

  • I think it's just brand, ubuntu was what I knew from using it as a personal desktop and then it's the default/most obvious option for a lot of providers, I think even 10+ years ago AWS EC2 defaulted to it above Debian, digital ocean too I think?

    I don't remember why exactly but it was definitely just 'linux VPS = Ubuntu' for a long time. I think they got reputation as being the 'just works' option because they were happier to include some non-free graphics drivers etc where Debian was the more pure option but most end users didn't care

    But since they added snap and I started running into issues with trying to install Docker etc a few years ago I default to Debian now and most of the time I don't even know which it is.

    • Stable Debian is using Linux 6.12, if your laptop has modern hardware what do you do? Can't use wifi?

      And don't get me started with Debian testing. I want a LTS distro not a testing one.

      30 replies →

    • Back in 2005-2008 or so, I think Ubuntu was a genuine breakthrough as a polished desktop version of Linux that set a standard that various other distros, eventually, caught up to. I think Cinnamon and other distros eventually caught up on polish.

      They also had credible commitments to long term support that brought people on board. I think that was enough to get them on the map, but personally as a desktop user, I haven't used it in a while, mostly sticking to Debian and Arch.

    • I think you are right about the branding / reputation. Personally I heard negative things about Canonical and I heard that they just basically follow Debian, so why not use the original? It's been a great experience so far. Perhaps because Debian moved to include proprietary drivers out of the box now it is extremely easy to set up.

    • Yeah this was the same for me. When I first made the switch to Linux for my dev machine Ubuntu was the distro I was by far the most familiar with so that was just the default choice. Later on after learning more and seeing how Ubuntu progressed I regretted not going straight to Debian.

    • For us slow kids in the back, can you link to a .ISO-file of your favorite Debian?

      Ubuntu found me (finally, with the tutorialhelp of a localLLM) in 2026, and I don't trust most of the opt-outs.

      25 replies →

  • > What is Ubuntu offering that Debian doesn't provide?

    Surprised how many answers here are on "social" reasons, and ignoring that Ubuntu does provide genuine additions to Debian.

    Ubuntu includes additional proprietary drivers to Debian. So there are legitimate hardware cases were Ubuntu will work out the box and Debian won't. I can't speak for how many people need those drivers, and how much of choice is down to defaults/inertia etc.

    From hearing interviews with PopOS folk, I think this is also a big reason people choose Ubuntu as a base for a lot of Distros instead of Debian.

    • Using Ubuntu as a base became popular partly for the hardware support, codecs, ease of installation. Typing this from Linux Mint, which offers both the default Ubuntu based edition, and LMDE (the Debian Edition).

      Debian has caught up, but it's been a minute since I've installed it.

    • How many of these additional proprietary drivers are needed on cloud servers, which are based on popular hardware configurations?

      What are the numbers of people still installing servers on the real hardware and needing these proprietary drivers?

      7 replies →

  • The traditional answer is that Debian is a bit slower-moving in both the Linux kernel and userland, so people who want current versions of popular software often find that they have to do some extra work in Debian.

    A gradually increasing number of popular userland applications have been publishing their own apt repositories however so this is less of a problem now than it used to be.

    Over the years though I've found that I much prefer Debian's relative stability and more thoughtful, if slightly plodding, release cadence.

  • Back in the day in 2008, Linux was niché.

    It had issues all the time, and finding solutions required searching online, manually. Time consuming, difficult process. Very un-beginner-friendly.

    From the throve of all possible distros, one stood out. Ubuntu. Very popular. Askubuntu Forums (with coffee beans denoting ranks) was the place when, 9/10 times, the answer to your problem could be found.

    So when your fedora friend cried trying to get his camera and sound working, you either found the solutions already, or asked for them and got them. Usually the former.

    That was the biggest advantage of Ubuntu. Big community and wealth of troubleshooting knowledge already available. And it had the opinion of a beginner friendly system. Which made the community grow and created a large market/userbase for help threads/tutorials.

    Add to that, that people are creatures of habit and 'voila - you have a lot of people sticking to Ubuntu just because they never got so pissed at them that they would change their distro.

  • Ubuntu is a Debian distribution that releases more often. A faster update cycle for their packages is basically their entire reason for existing.

    I may be biased as a Debian user, but if Ubuntu now reacts slower than Debian this may push some people to reconsider their choice.

    • If we compare Debian Stable to Ubuntu LTS, it's the same update cycle.

      So Ubuntu LTS is pretty much Debian Stable with some different defaults (more opinionated, for better or worse).

  • For me it's just because I've been using Ubuntu full time since 2008 and has served me well my entire career, I think it's fair to say it's the flagship desktop OS that introduced many to Linux.

    I feel like we're close to a post-distro era of operating systems though. My ansible playbook customizes so much already it wouldn't take too much more to just start from debian tbh.

    • Me same. I'm on ubuntu since 16.04 and it's annoying switching, because I'm used to it so much. Definitely switching on Debian, because they're not shipping software through apt anymore (eg. browsers). I'm running that through nix right now, and I don't want to deal with this nonsense.

      3 replies →

  • For me, it's not so much "what does Ubuntu have that Debian doesn't" and more that "just use Ubuntu" has only bitten me twice.

    It's 2009 or so and I want to try Linux. "Just try Ubuntu" they say, and I have a good time. I see that many "How to use X on Linux" guides, or FOSS software, often build for only Debian, and sometimes only Ubuntu. This is fine until snaps give me huge problems in 2018, and so I completely stop using Ubuntu desktop.

    Now in 2026, I manage three servers (two on Ubuntu), one Raspberry Pi (on Ubuntu), and two Linux desktop installations. I stopped using Ubuntu desktop in 2018 but snaps are less problematic for my server workflows, so now I have three Ubuntu server installs. On my desktops and my one non-Ubuntu server, I find myself sometimes missing Ubuntuland. (These aren't Debian though, so I might just be missing Debianland.)

    "Just use Ubuntu" is now something that has bitten me in using servers. Two bites in 17 years is a fantastic track record. But this slow response to a CVE fix has me looking at Debian, and this has shaken my faith in canonical. "Do they pull in upstream security fixes quickly" is one of my first questions for any FOSS I use.

    But my servers aren't Nix or IaC or whatever, and so... Taking them down and putting them up would take a lot of time and risk, which are two things I'm not so willing to spend. Maybe it's 10 minutes, or maybe there's a bandaid fix I have from 2023 that I forgot about and would need an hour to re-derive. So, I find myself taking the security gamble instead.

  • Ubuntu offers a path from free use to paid first party support. For me, that makes it very attractive for a startup or small business that may want to add a support contract later. Ubuntu makes it a lot easier than Red Hat. Paid support for Debian is via third parties. Ubuntu is a solid distro, although I think Debian is a better one if paid support isn't an important feature to have.

  • Ubuntu has a timeline for how long they will provide updates for a given long term distribution release. I moved over to Ubuntu back when CentOS was converted in to a Fedora type release without a long term commitment to providing security fixes.

    I might be moving over to Rocky Linux 10.

    • This is the big reason that I see a lot of companies using it over Debian.

      Five years of guaranteed updates, with an option to pay for another five years ticks the box for accreditors and the like.

      The much vaguer Debian policy that a release will be supported for some undetermined period based on how frequently they release, and then get some kind of volunteer-based LTS support for a couple of years after that, and then maybe further through some third-party ELTS program is a much harder sell.

      1 reply →

    • We migrated to Ubuntu from CentOS as well. It was simply because Rocky wasn’t established enough at the time and we haven’t had a reason yet to again look elsewhere. Tho we haven’t also phased out most VMs for containers of some sort.

  • Install Ubuntu and you get 10-15 years of support of your current software stack.

    Install Debian and you get 3-5 years of support.

    Ubuntu also invests a lot into their desktop experience while Debian is closer to stock Gnome. That's more of a preference thing, though.

    Debian has also traditionally been a pain to use with proprietary software. Nvidia drivers, WiFi firmware, you name it. It got better in the past years but it's hard to shake the bad name.

    • > Ubuntu also invests a lot into their desktop experience

      Unfortunately that's been dwindling. Canonical seems to be focused on servers and virtualised instances. The desktop experience is stagnant.

      2 replies →

  • Historically, Debian didn't ship proprietary wireless firmware in the installer (because it was proprietary software, and Debian doesn't do proprietary), so you couldn't install it on most laptops without plugging them into wired Ethernet to download the wireless firmware packages from non-free.

    They changed that a few years ago, but plausibly the underlying prioritization of end-user experience is still lower than Ubuntu's degree of user focus.

    I still wish Mark would rename his company "Ubuntu". He's a great guy, the company does great work, but I keep getting undeserved credit for it because we wouldn't sell him the domain name.

  • For some reason I had feeling that Ubuntu more "serious" than Debian. I mean they're asking for money from people. So it's basically Debian with paid services. Can't be worse than Debian and probably is better, maybe they paid some engineer with these money to patch things faster.

    That's just some rough reasoning in my head.

    Also when you install third-party software, 100% of them will support Ubuntu. That's more about workstation usage, though. But having tested platform matters.

  • How is the gaming experience on Debian? I'm genuinely asking, not a snark.

    I use desktop Ubuntu because it's up to date and it just works for me, and I can play the latest games in it with Steam + Proton. I don't have to tweak it or do any additional downloading of stuff besides the Nvidia drivers (I actually don't remember how I installed them).

    Can I do this with Debian, in a no fuss way? (I know this can be done in any distro, that's why I'm stressing "no fuss").

    • Nvidia proprietary drivers are generally pretty old. I did some messing around with the CUDA packages to get recent desktop drivers in order to run some games.

    • Right? Can I install Debian and have Steam work as well as Ubuntu? Can I install Debian over my Ubuntu (without pain) and keep my dual boot with Windows 10 situation? If yes to both, will consider!

    • In my experience, Linux distros on older kernels sometimes struggle with modern hardware. Especially with newer devices, features and especially bug fixes take a while to make their way to the distro.

    • I believe Steam just works as long as GPU drivers are working.

      On Arch I just installed the flatpak and didn't think about it, everything works.

  • I find major version upgrades a lot more reliable on Ubuntu. Every time I've done that on Debian something big broke.

  • If your infrastructure doesn't use landscape, kernel hot patching, JuJu or similar Canonical technology, or doesn't have its own Snap storefront, there's no need to install Ubuntu. Rest is just momentum.

    Debian used to move a bit slow in terms of userspace, and that's true, but for servers, that's a non-issue for the last 20 years or so (from my experience).

    On the Desktop side, Fedora and Ubuntu moves faster on the userspace front, but if your system is behind a NAT, and you know what you're doing, Debian Testing is just as good, more stable and it's rolling (except when it's feature freeze, but a stable workhorse is better than a shiny but breaking one).

    Debian allows me to sleep well at night, provides guaranteed updates, and works rock solid all-round, so I won't be touching Ubuntu for the foreseeable future. Esp, with controversial choices like uutils, etc.

  • I would need to reinstall OS on my laptop and deal with all time-consuming migration stuff for everything that changed and to configure Debian where it is doing weird things

    > What is Ubuntu offering that Debian doesn't provide?

    I have it right now at zero additional effort

    • This is now trivial with agentic tooling. I recently used a separate laptop and VM over a weekend with an agent to complete a full migration. Cost is hours and a dollar in tokens.

      3 replies →

  • Proprietary drivers, desktop first experience similar to how Mandrake used to be, or SuSE, and the most relevant, in regards to proprietary software on Linux distributions, it tends to be either Ubuntu or Red-Hat.

  • Speaking as somebody who stayed on it way too long (until 10 years ago, maybe) it was because people constantly told me scare stories about how difficult it was to configure into something usable.

    I had to go through the torturous path of Ubuntu -> Mint -> Mint Debian -> Debian. The last step was after I used a Debian live disk to do something and I could see that the stories were nonsense; just something that had adhered to the word Debian in my mind through repetition.

    The two worst parts about it were 1) that I had long left Ubuntu on servers and had been using Debian there for years - I was just afraid of the desktop for some reason, and 2) that if I had just listened 15-20 years ago when people told me that FrankenDebians were nothing but problems, I would have never been caught in the net.

    I've never been a fan of Ubuntu's business practices, but I'm just generally not into Debian derivatives anymore. If I were to leave Debian, it would be for an entirely different (and philosophically different) distro. I probably make an exception for Devuan, because it's only trying to change one thing (that I think of as the biggest threat to Linux, the final boss evil spawn of RedHat.) Devuan is an escape hatch for when the rugpull happens.

  • At my company, it’s the pateena of “enterprise”. I came to th company with strong open source bias. The more traditional/conservative IT guys were all about Microsoft and RedHat. When I lobbied hard for some Debian assets, Canonical was the compromise. But I think we’re real close now to seeing the next round of allocations be straight Debian.

  • > What is Ubuntu offering that Debian doesn't provide?

    I'm on an nvidia jetson which comes out of the box with Ubuntu pre-installed (it's slightly more complicated but that's the gist). You can run other OSes but it is a messy experience and you can easily run into problems.

    Yes, it is shitty from nvidia that they do it this way. But it is also convenient.

  • It's just the default target. For backend stuff, you're right that there's really very little true value. But client software just has a lot of complexity. If you run binaries from wherever, they're probably built and tested on Ubuntu first. Like, your vendors won't support distros officially, install scripts and AppImage integrations are going to tend to assume stuff. Driver/runtime integration for things like binary GPU stacks are going to document Ubuntu first. If someone makes an assumption about Python version (a personal peeve -- LOTS of python software ends up lagging the tip, it's not a super compatible ecosystem), it's going to be that you're running Ubuntu LTS version "one before latest", etc...

    Are those fatal flaws? No. But lots of people just don't want to deal with it. And there's a market for that.

    • I can't think of anything I've ever had trouble running on Fedora + containers, with the latter typically for proprietary software that depends on specific or ancient userlands, or simply to avoid cluttering up my base system.

      1 reply →

  • I used Debian on my machines (after I got past their ideological view on drivers and found I could get them separately and made it work) ... until a patch came out and WiFi was broken on my machines. I went back to Ubuntu, have not had issues like that. Ubuntu works reliably, from my experience, on real world machines.

  • Ubuntu did what Debian failed at. Better LTS, More features including drivers, available by default by most providers, lot more branding/documentation and in the early days, easier distribution. I am old enough to remember distro like SuSe Linux etc and when Ubuntu came on scene, it became the de facto.

    • Debian's modern release cadence and optional backports seems to have turned this around, to a degree.

      I moved all my new server/service deployments back to Debian around 2021/2022 (bullseye era).

  • Just that it’s already installed, and I haven’t tried a new distro in over a decade.

    But 15-20 years ago it was easier to install the nonfree stuff on ubuntu, like drivers and DVD playback and stuff. I don’t know if its still like that.

    I never understood ubuntu as a server over debian, but for a desktop it was a nicer experience for a while.

  • They test run a little more tests on their backports (and have the manpower to actually look into what is failing) and they have really far out EoL once the kernel release is selected at fixed intervals. So if you managed to get the capabilities that you care about in their tests, there is a low probability that applying updates will cause some catastrophic outage or data loss over the next 10 years. Which can be improved further by fine-tuning phased update rollouts.

    Unfortunately, they did in recent history manage to still break iptables, zfs, nilfs and a bunch of machines with weird (arguably broken) firmware anyway, so my personal comparison between Debian (or simply directly the Kroah-Hartman/Levin stable upstream) and the Ubuntu backports is not exactly in favor of Ubuntu.

  • For servers, livepatch, latest ZFS and ZFS-on-root supported ootb, faster release cadence

    For desktops, gaming and commercial software support, "it just works" (my fresh install of 26.04 with Wayland, recent WiFi, HDR+VRR, i didn't have to fuss with anything)

    For laptops, I've routinely had issues in the past where Fedora or Mint wouldn't work ootb when Ubuntu did.

    And then since it's what I'm used to on my server and my desktop, i just use it on my Pis and WSL installs for consistency.

    I still try out other distros occasionally and i do run Debian on some specific VMs for various things, but I've just had relatively few issues with Ubuntu, been using it for >10 years, and don't see any reason to switch.

  • In my case, I started using Ubuntu like 10 years ago because the desktop experience was much more polished.

    For example, the fonts and the font rendering in Ubuntu and its derivatives were noticeably better than on stock Debian/Arch/etc.

  • Debian by default has had ancient versions of stuff, and if you want third party software, Ubuntu has more mindshare so it was more likely to be tested - anything from graphics card drivers to Steam games.

    • It hasn't. Debian has releases every 2 years, same as Ubuntu LTS, and packages are up to date at the point of release.

    • and of all those patches, the ones that have staying power get upstreamed as Debian packages all over again.

  • [for clarity, I am not talking about servers]

    When a non-technical person asks me “which Linux?” I recommend Ubuntu because it is about as gentle an experience as Linux is going to be. The install is friendly and the culture is less RTFM than anything else.

    Those are the same reasons I run Ubuntu on my laptops that aren’t running Windows…I prefer low friction to arguable technical superiority. I’ve looked at other distros in the past and decided they weren’t worth the bother…To Me.

    But that’s me, not you or anyone else. And my use case not yours or someone else’s.

  • I always assumed the software is newer. You can update to a LTS more often, if your server needs that. For example, I think podman adoption is hampered by Debian's slow release cycle. Trixie finally supports quadlets.

    Debian often ends up as Frankendebian, or with custom repos added. How do you run e.g. Nextcloud on Debian? Where do you get the new php version required for the upgrade from? Right, there is a community repo somewhere...

    • I should mention this is maybe not an issue for servers with containers, nowadays. And desktops have marketplaces and linuxbrew.

      But it took 3 years from Debian 3.0 to 3.1, then 'testing' was frozen for 2 years. A lot of users were lost to Ubuntu at that time, which released every 6 month.

  • Consumer-centric customizations and non-free package options. It’s somewhat akin to answering “How can I add stuff like OneDrive to Linux and not have to configure/self-host everything?”

    I used to like Ubuntu and Canonical products and these days I’m more indifferent towards them. Their products have a place, but I wish Canonical would stop killing off some of the more interesting side projects.

  • I'm not a Linux user, but occasionally self-host some stuff. One time I tried Debian instead of Ubuntu, it was a lot of "this is not installed" & "this is not set up" errors during setup process of software I wanted. In the end I succeeded in doing what I wanted, but I also wasted time on doing things I never have to do when using Ubuntu.

    • But we're talking about running a server in production here.

      If one can't be bothered to install what is needed, maybe one should not run a server in production?

      Quickly running something on your LAN for testing is different, but if you expose it to the Internet, probably your main concern shouldn't be "this is not installed".

      1 reply →

  • MySQL. You can make a totally valid argument that sites should just switch to Maria DB instead, but there's also no doubt that dropping MySQL support from Debian cost it a lot of LAMP servers. That, combined with Debian's release cadence which made it difficult to run numerous PHP apps basically pushed LAMP servers to Ubuntu.

  • For desktop use, new-ish user-facing packages without any hoops (such as backports) jumped. Especially where collaboration is involved it can be a major issue when a program lags behind its commercial OS counterparts by several months or years in terms of features and behavior.

    I don’t use Ubuntu but use Fedora (and its derivatives) partially for that reason.

  • Familiarity. Many Ubuntu people(who were introduced to Linux via Ubuntu) never change horses. I am speaking about IT people not common folks.

    You and I know Debian isn't much different, they don't know cuz some never investigated. I say some because they landed in a role with a company that is Ubuntu and never had reason to learn anything else.

  • >What is keeping people on Ubuntu instead of just using Debian?

    1. It uses much newer packages and people want shiny

    2. It was marketed as one of the easiest to use linux distributions maybe 15yr ago or whatever, so a lot of new people and then tutorials went to it because newer software and features just worked.

    3. What is keeping them on it now? Familiarity. Inertia.

  • They probably don't know Mint was based on Kubuntu. Or that they all - like DSL, Knoppix and others are all based on Debian and if you're brave, you can pivot to Sid from each of them.

    When I worked at Canonical, the funnel I observed was Gamer Culture and the Chronically Online. They don't know from Debian.

  • I only run Debian personally, but my dayjob company runs on SQL Server, and the officially supported options there are Windows Server, Ubuntu, or RHEL. It's not worth the effort dealing with management/auditors/etc. to try to run our prod DB on a non-supported platform.

  • Ubuntu is the gateway drug to Debian, in a lot of ways. You get used to GNU/Linux with Ubuntu, then you find out that there are more refined options and go for those, and a not-insignificant part of that crowd likely goes to Debian because of how familiar it is.

    • Careful, lest someone's going to mention Arch.

      I agree btw. But I've been using Linux since end of 90s (I barely made use of the 2.0 Linux kernel series). I quickly established on Debian in the Potato/Woody era. Debian, back then, was severely slow with new releases. So I ended up with Testing. Which got slower security updates than Unstable. Which sometimes broke (like any rolling release does). Back then Ubuntu got released (we talking '04 and '06). And I just sticked with Ubuntu. On servers, too. I endured it all, including the Amazon spyware, the ads in MOTD, and the switch to an inferior in-house software management for some package (which name we won't mention).

      2 replies →

  • Because every where you used to go on the internet you read that debian is “slow” on updates but stable as a trade off, if you are after certain new packages you have to use Ubuntu, also, some use cases (say jetson boards) have ubuntu by default plus nvidia drivers.

  • For me, habit. A habit I'm getting tempted to break by exactly the grumble in this post. This has been an awful ~two weeks for maintaining infrastructure and the ubuntu lag on this specific issue is contributing to the awfulness.

  • Enterprise support contracts for Linux and the compliance legal liability. No large commercial companies would run purely contributor supported systems because of the lack of those two things.

  • It's the default that a bunch of vendors package. For example, Nvidia's official CUDA images used to only be provided for Ubuntu (they have since expanded their offerings somewhat)

  • Desktop Ubuntu purely because of the drivers. Normally used Debian for my own servers, but haven't done that in so long, and Ubuntu is often default on cloud providers so yeah.

  • It’s the default offered by most cloud providers, so in some sense it’s pure inertia.

    I really don’t care what I run on, as long as it’s some flavour of Linux, it works reliably, and it’s secure.

  • Mostly:

    1. Hardware generally just works

    2. Videos that use patented formats just play without fiddling

    3. Proprietary closed-source software, if they even support Linux, usually releases Ubuntu binaries before anything else

  • FIPS mode? It's a pretty niche requirement, but I was under the impression that options are somewhat limited for FIPS-compliant crypto (both disk and networking)?

  • Back when I used Ubuntu it was because I was tired of being excited about a new feature and not getting to use it until it made its way to Debian 5 years later.

  • Suppose you are an enterprise paying large amount of money to NVidia to buy their AI hardware to run AI workloads locally. Are you going to say we will refuse the default OS (https://docs.nvidia.com/dgx/dgx-os-7-user-guide/introduction...) on such hardware and lose hardware support, or are you going to stick with the supported OS for your hardware?

    Enterprises care far more about vendor support than the typical Linux hacker at home.

  • Software, such as AMD Vivado, tends to support Ubuntu more than Debian by testing against Ubuntu only. Nvidia's Jetson stack supports Ubuntu.

  • Ubuntu's remote OS upgrade feature exists and works pretty well in practice. I am not saying this is enough to stay but it does exist.

  • All my servers were debian until I brought some Raspberry Pi 5 boards. Debian still does not have tested images for them today.

  • Inertia, I'm guessing. I have a couple of older on-prem servers still on Ubuntu LTS. Newer ones are on Debian stable.

  • Approx. two years ago I saw a teacher at my IT school trying to install Debian on a students virtual machine, side by side to a Windows 11. Just for fun, while watching them, I installed Ubuntu side by side on my virtual machine. These two were not done after three sessions and ultimately failed to install Debian. The installation GUI was full of cryptic words I never heard of and looked like from the year 2000. Meanwhile, the Ubuntu installation went flawless. it was done in under 15 minutes, the GUI looked modern and sexy. All I had to do was enter a nick and password, and drag a slider to tell the procedure how much space I want to reserve for Ubuntu.

    I hope that answers your question.

        ¯\_(ツ)_/¯

    • How is that possible. You can just press enter during the whole install except the prompt for wipeing the HD where you need to select Yes do wipe it.

      1 reply →

  • ROS, which is not officially supported on Debian. Not using it myself, but users here do use it.

  • Please suggest a better alternative for a cloud server? (Genuine question, where do I move?)

  • 1. Faster and predictable release cadence. New releases every six months, April and October (hence x.04 and x.10). New LTS releases every April on even years (26.04, 28.04, 30.04, etc).

    2. The LTS releases are supported by Canonical for at least five years on the free tier, and up to fifteen years with paid support contracts.

  • They have more kernels, more support for modern hardware etc... good luck running Debian on a modern laptop.

    Ubuntu kernels are not the one that Debian uses. The latest stable Debian is based on a 2 years old Kernel ( 6.12 ).

  • "Ubuntu" is an ancient African word meaning "I can't configure Debian."

    • If it's a corporate computer you don't want to deal with manually configuring stuff. I also want as little manual configuration on my personal machines, hence why I use Ubuntu.

>Oh and btw, distros run by volunteers (Debian, Arch, Alpine...)

And Slackware too:

    Thu Oct 22 23:04:17 UTC 2026
    patches/packages/linux-5.15.223/kernel-generic-5.15.223-x86_64-1.txz:  Upgraded.
    patches/packages/linux-5.15.223/kernel-headers-5.15.223-x86-1.txz:  Upgraded.
    patches/packages/linux-5.15.223/kernel-huge-5.15.223-x86_64-1.txz:  Upgraded.
    patches/packages/linux-5.15.223/kernel-modules-5.15.223-x86_64-1.txz:  Upgraded.
    patches/packages/linux-5.15.223/kernel-source-5.15.223-noarch-1.txz:  Upgraded.
      This update fixes bugs and security issues, including the PwnEscape flaw.
      For more information, see:
        https://www.cve.org/CVERecord?id=CVE-2026-99999
      (* Security fix *)

From: https://ftp.osuosl.org/pub/slackware/slackware64-15.0/Change...

  • Slackware is a cool distribution. I really love that it's maintained by Patrick and I enjoy the simplicity and the stubbornness of it's opinionated decisions.

    I stopped using it back in 2004 when Patrick had health problems. It seems to be a passion project and it stopped getting updates while he recovered. There is a community behind it but it may mainly be driven forward by him.

    It looks like it's fairly slow to get updates, generally, as the last release was Slackware 15 in 2022. Maybe that reflects it's dictator (his word not mine) or maybe it reflects it's stability.

    Yet, despite all that, Slackware got this security fix around 10 days ago.

    • Slackware-current or slackware-current64 is the main release channel. https://mirrors.slackware.com/slackware/slackware64-current/...

      There's dvd iso's available the slackware-current branch, usually built about once a week by AlienBOB

      Guess you could call it a passion project, but after all these years of dedicated tireless work that seem to resemble more of a machine than man, seems that doesn't completely sum it up. Hope he keeps it up, its pretty much the only pure distro left (or maybe I dislike systemd that much)

You get a very different CVSS score depending on the formula you use. Ubuntu's response page lets you select between the two.

(I think CVSS is a very poor metric in cases like these; I'm just explaining what I think Ubuntu's process/position is, not making excuses for them. My read is the 9.8 is probably too high but nevertheless more accurate in this case.)

I moved over to Debian and haven't looked back, years ago. Why anyone would prefer Ubuntu over Debian, which is a purer, higher quality, more mature distro, is beyond me.

  • > Why anyone would prefer Ubuntu over Debian, which is a purer, higher quality, more mature distro, is beyond me.

    For me, I view Ubuntu as the "higher quality, more mature distro" which I value over "purity".

Well, I did it. This was the straw that broke the camel’s back: I have moved over to Rocky Linux. Took me maybe four hours to do the full transition.

I am more a RedHat user, and Ubuntu never felt really comfortable for me. I don’t like having to do incremental upgrades every two years or so; I would rather do a single big upgrade about once every 7-8 years and have a rock solid development environment. Also, `dnf` is simpler and more stable than the mess of `apt-get` and `unattended-upgrades`.

  • > Also, `dnf` is simpler and more stable than the mess of `apt-get` and `unattended-upgrades`.

    I'm not saying you're wrong. I am saying that this is a new sentiment I've never heard expressed before. Perhaps Ubuntu's done something to make it flaky, but the upstream Debian apt tooling is famously stable and boring. I'm saying this very seriously: I don't recall a single time, ever, in about 30 years of using Debian-and-friends, that I've ever been bitten by a bug in apt-get or apt. I have also never been hit with a dependency bug when I wasn't using dodgy third-party package sources. In the many situations where I've deployed pure Debian (or pure Ubuntu) servers, `apt update && apt upgrade` has worked 100% of the time.

    I do not claim that no one's had problems with this. The world's large. I'm certain there are people out there who have nothing but trouble with apt and friends. I do claim that I've never personally seen that our been in a conversation with people who have.

    • `unattended-upgrades` was frequently giving me Python warnings in Ubuntu 24.04 about how `fork()` should not be called. `apt-get` has given me issues, years ago, where it would pull up a crappy full screen text UI asking me (usually irrelevant) questions about some update it was doing, and the entire update process was halted by those questions.

Worth noting that RHEL, the Linux version Red Had sells licenses/paid support for, also didn't update it for weeks

Did Ubuntu Pro customers get the fix?

  • I think this is the important question. To everyone who is complaining while using Ubuntu for free: People whose software you use for free don't owe you anything.

    • Of course they don't owe them anything. Ubuntu's reputation is built primarily on people who use it (or used to) for free. They are/were Ubuntu's advocates and what made it popular.

      So just as they made it popular, they can make it unpopular. People like me will simply post on our blogs and social media that they should not install Ubuntu. A typical Ubuntu user is not that high on the tech scale, and they listen to people like me for suggestions on which distro.

      Cut the pipeline that feeds into it.

I've switched my default to AlmaLinux. Was a fan of Ubuntu since 8.04 (Hardy Heron) but stopped since Canonical pushed hard on Ubuntu Pro.

  • I don't like ads, and I didn't like logging into SSH and seeing a nag to update to Ubuntu Pro because I had the balls to keep running 20.04 in 2023. I've seen this before on previous releases (and know how to remove the message), but seeing it again was the straw the broke the camel's back.

  • AlmaLinux is "boring" in the best possible way, and it works really well in WSL too. Their extended support for x86-64 v2 has also been useful on one my old computers.

This is the straw that broke the camel's back. I am moving back to Debian stable now. Having NVIDIA drivers and Wlan drivers back in 2014 was great, but this is not acceptable.

I have had some thoughts about switching to Fedora for my daily driver laptop - but as far as I can see I would not be better off in this case with Fedora? I cannot see that they have shipped a fix for this either?

Same with the recent PHP vulnerability Debian had the patch ahead of time. Ubuntu had it many hours later...

I think this is more of a communications failure than anything. My understanding (happy to be corrected) is:

1. That for this to be a DOS type exploit, the attacker needs to exploit a race condition over network, which is an incredibly unlikely event that one can't really force.

2. For it to be a root exploit they need to craft the IP options with a specific memory address, but that memory address isn't known to the attacker because it's not a constant (see KASLR).

3. There is also a simple fix by simply adjusting iptables, and much/most/many network setups already drop IP options by default.

If I'm misunderstanding something let me know, but in practice this doesn't seem like it's likely to cause much damage. The people at Canonical and Redhat probably came to same conclusions and are balancing the true risk (not CVE risk level which are not very useful) with the potential for introducing a regression for their customers. This kind of stuff happens somewhat often and never catches fire like this, I think Anthropic is just fanning the flames and Ubuntu is taking the heat.

  • Revision: It seems like catching the race condition is not that hard, but the root exploit is very unlikely. But still, the fact we haven't seen lots of services going down indicates to me that this is overblown.

The "WTF" is unwaranted, it's really not that easy to write a weaponized exploit for a bug like that one.

I am a bit surprised by the panic...

Its only the media / publicity that drives this one, there were worse within the last year that nobody seems to care about.

  • That is with the implicit assumption that the mptcp exploit of this ipv4 tcp bug is the only exploit that will be found. I don't think that assumption will hold true.

    • There were other fragmentation flaws that were equally as bad as this, I wrote the reproducer.

      IIRC it had minimal HN discussion.

I have been thinking of moving to NixOS from Ubuntu. Are they any better on security updates?

  • Yes, NixOS has already patched this.

    NixOS also makes it much easier than ubuntu to install your own patches and version of the linux kernel.

    For example, assuming NixOS had not yet released the fixed linux version, 6.18.56 (though it has), you could upgrade to it before NixOS did it upstream with this one line:

        boot.kernelPackages = pkgs.linuxPackagesFor (pkgs.linux_6_18.override {argsOverride = {src = pkgs.fetchurl {url = "mirror://kernel/linux/kernel/v6.x/linux-6.18.56.tar.xz"; }; version = "6.18.56"; modDirVersion = "6.18.56";};});
    

    You could add the patch yourself if you needed to with:

        boot.kernelPatches = [{ patch = ./cve-patch.patch; }];
    

    And then you'd be updated.

    The debian and redhat based distros all make it so configuring what packages are installed ('apt install' / 'yum install') is a different operation from configuring the packages themselves.

    On NixOS, the specification of how to build a package, what package is installed, patches, etc are all in the same language, and so it's a lot more natural to patch things as needed.

    And also, LLMs are pretty good at generating working nix, so you can have an agent apply patches to your kernel package with NixOS quite easily. Agents can also do this for ubuntu or redhat, but in my experience they're much worse at it, and it's harder to undo mistakes if they mess up.

  • Substantially worse in my experience. They build the whole OS in CI which is slow and unreliable, and as a result it can take 2+ days for updates that other distros have out in under an hour. You can try mix packages from smash or unstable builds but for stuff like kernels that’s not simple.

    • The quantitative data we have shows that NixOS is fresher than other distros in general by a significant margin.

      See https://repology.org/repositories/graphs

      If you pick a specific random package update, nixpkgs often has that update months to years before other distros.

      If you pick a specific CVE, nixpkgs usually is better with the exception of embargoed ones, where Ubuntu, Fedora, etc get to prepare their patched packages ahead of time.

      1 reply →

  • (~10 years NixOS user, and committer.)

    It depends.

    Mostly on how much rebuilding it needs (e.g. if it's a "leaf" package, or one many packages depend on).

    The merging of security fixes is usually very good, also because it is so easy for anyone to just make a PR.

    The security team also seems pretty competent and fast.

    As a sibling commenter says, it is also extremely easy to just apply patches to your own system in general, usually with a few line of easy code max. So you can fix systems without dependence on distro maintainers.

    In contrast to e.g. patching a `.deb`, you can declare the code such that the patch will still be used even if the distro releases a new package; you can carry the patch forward, and don't need to choose between {not having the patch because the distro lacks it} and {not having future security fixes because you pinned your custom .deb version}. NixOS will rebuild any future update, applying your patch to it. That's a big benefit, because it makes "out-of-tree" custom patches very maintainable.

    Due to declarativeness, you can easily roll out your fix on lots of machines.

    Also, the "SBOM" (software bill of materials) part is quite good in NixOS. It's very easy to determine which package uses what dependencies.

    The only real drawback is CI build time when a high-dependency package needs fixing.

    Due to the way Nix works with its immutable hash DAG of package dependencies, a package change will trigger a full rebuild of all packages that recursively depend on it.

    For example, if you change 1 line in glibc, or libpng, or curl, or (recently) brotli, the entire distro needs to be recompiled from source ("rebuild the world"). Some of the packages, such as Chromium, can take many hours to rebuild individually. Rebuilding all-of-NixOS can take days.

    In distros that can mutate packages without triggering dependency rebuilds, updating 1 line in e.g. glibc, will only rebuild that package, allowing to theoretically distribute such security updates within minutes (if done, see Ubuntu counter-example).

    The mass-rebuilding is done by NixOS's binary-cache build farm. A new NixOS update is generally only released once the build farm has fully built all dependents. (One can also opt into a "small" channel that releases as soon as only a few core packages are built, which gives you security updates faster for those. But if you do that, your computer will next start compile all huge packages such as Chromium, in parallel to the NixOS build farm already doing that. So usually people don't.)

    For the recent brotli CVE-2026-111497, the timline was:

        2026-10-21       node.js releases its fix for node2shell (caused by brotli)
        2026-10-21 19:27 https://github.com/google/brotli/releases#release-v1.2.1
        2026-10-22       brotli CVE-2026-111497 gets published
        2026-10-22 06:51 PR "brotli 1.2.1" https://github.com/NixOS/nixpkgs/pull/577208
        2026-10-22 08:25 PR merged to "staging" that will become rolling "nixos-unstable" in the future
        2026-10-23       created https://tracker.security.nixos.org/suggestions/by-id/60353
        2026-10-23       created https://github.com/nixos/nixpkgs/issues/577796
        2026-10-28       CI has built a nixos-26.05 update that includes it:
                         https://hydra.nixos.org/build/351243680
                         This is the point where users can install it.
        2026-11-02       CI for rolling-release nixos-unstable is still not built, 2 weeks later:
                         https://github.com/NixOS/nixpkgs/pull/577208#issuecomment-6573335016
    

    So in summary:

        The PR got made within 7 h
        Review and merge happened within 2 h
        CI took additional 6 days for stable NixOS 26.05
        CI for rolling nixos-unstable is still not finished after 10 days post-merge
    

    For our startup, I rebuilt the slice of the world we use on a 16-core CPU within a day or so, without waiting on the NixOS build farm to build all of NixOS, so we got the update significantly faster.

    Also note that just patching a library in your distro is often not enough. For brotli, lots of upstream package vendor brotli's code. NixOS contributors seem to be quite good at looking at underlying issues, e.g. there's this issue "Tracking vendored Brotli decoders" (https://github.com/NixOS/nixpkgs/issues/578375) to track that. I am not aware of other distros making such efforts.

    Thus:

    In NixOS, security updates are great and fast for leaf packages such as the kernel, but can be slow for many-dependents packages. Much of that can be mitigated by building things yourself, which is easy.

    Hope this helps.

This is a valid concern.

AI is now capable of, and being applied to, find so many bugs recently that infrastructure providers need to up their game and respond quickly.

Hopefully this is a passing phase as bugs are quickly patched, and we'll get past it without too many incidents.

A nation state actor behind a popular linux distro got discovered with keys to the kingdom and they scramble to keep their option open, while acting as if nothing has happened - that's how I see it.

On desktop, Debian stable has been excellent as of Debian 13. Ubuntu was good until 2018, and has since been sluggish and slighy buggy.

I highly recommend Debian. Breath of fresh air and freedom, compared to windows and MacOS.

  • +1, switched to Debian with 13 since it got plasma 6 earlier. Much better experience- no snaps, gnu utils, stable. It's everything I want from the OS.

E.g. Ubuntu 22.04 Linux kernel 5.15.0-203.213 was published in Canonical's proposed kernel PPA on October 26, 2026. So just enable Canonical's proposed repository, use APT pinning to prevent automatic installation of untested packages and install the patched kernel. I agree that they need to get quicker at pushing these updates into stable, but it's not as if you don't have a choice.

It’s not a good look that Ubuntu is taking its time with this patch even for paying customers, but I do have to question how widely exploitable this is. If your site is mission-critical, it most likely has a load balancer or reverse-proxy in front of it that’s probably already filtering it out. Companies like AWS have already confirmed that their load balancers filter it.

Remember that the AI companies benefit from creating panic every time there’s a new security exploit.

What would you recommend to use on servers? Would you host you apps off Arch? Or better to take Fedora or similar? I am genuinely interested in answers not distrowars

  • After painful Ubuntu upgrades in the past, I moved to Alma Linux and have been very happy. It takes a small adjustment to dnf instead of apt, but realistically I was over that hump in 30 to 60 minutes and this was before AI. With AI to translate and test install scripts and the like, it might be a 5 minute task depending on how much automation you already have in place. Though even an entirely un-automated setup that is just a README.md, claude wrote me an Alma Linux version of a very ubuntu specific project that gave instructions for Alma instead of Ubuntu, and it worked almost perfectly first time and AI was able to (with prompting) see the issue and quickly found a workaround. We're a small org, but at some point when we hit scale and have compliance requirements, a migration to RHEL is also largely trivial if/when the time comes.

  • Good question... I run ubuntu on servers because the LTS has clear 5 years of security fix.

    I use arch linux for my NAS because it's fun and I don't care if it occasionally goes down but I wouldn't use it for production (on my NAS it's mostly stable but has gone down a few times)

    So what's next? Centos is a rolling upgrade, nixos?

  • As always, it depends on how and what you're managing on it.

    VPS/VM? Debian is a great choice. Use it as base and run your software via systemd+podman if you want the most up to date stuff, Debian tends do lag a bit. It is very low maintenance.

    Bare metal? Fedora Atomic is awesome. It does require an update every other week since it keeps packages closer to upstreams, but this is where the immutable base shines, any issue is an easy reboot to revert. Also systemd+podman for your own software.

    I wouldn't recommend Arch on servers.

    Edit: clarified Fedora immutable spins are called Fedora Atomic.

    • Note that Fedora CoreOS is a very low maintanance atomic Fedora system designed with fully automated updates in mind, and along with the systemd podman integration you mention, can easily be set up to automatically update both OS and containers.

      Which may not be ideal for serious production workloads, but is perfect for non-mission critical appliance workloads like Pihole.

  • I use Arch for servers too, for almost a decade, and to my memory only once I had an issue. That was booting off an encrypted RAID and some change which needed some investigation and then reconfiguring. I am planning to run them servers on Arch for as long as I can. It’s a bliss to never upgrade my system (only update it).

    • Similar. While theres something to be said about declarative and immutable distros, if you're not going that route a minimally opinionated distro works a treat for server workloads.

      And besides, just about every workload you can containerize should be containerized. Ideally though many with more isolation than what plain old runc provides.

I'm switching to Debian for my companies and personal projects.

For 15 years or so, I used and recommended Ubuntu. But this is unacceptable and I won't be looking back.

For people who absolutely need to run 16.04, 18.04 and 20.04 without any further subscription, I recommend installing the signed kernel from 22.04 (as of right now only available in the -proposed repo). Worked fine for some 16.04 examplary machines I had around that are stuck and bumps the kernel to 5.15 (soon EOL, but maintained by ... canonical, to get security patches).

It is strange, agreed. I just manually mitigated it using Claude and also blocked ipoptions at the router and in every node iptables.

If anyone is moving away from Ubuntu, I suggest NixOS, especially with LLMs. You will be able to build the machine of your dreams.

> ...distros run by volunteers (Debian, Arch, Alpine...) have shipped the fix. Meanwhile Ubuntu, made by a company that sells security subscriptions, hasn't.

This tells you all about the priorities of companies. It's making profit, not protecting their users. Perverse incentives and all that.

I genuinely want to understand why people use Ubuntu, and especially for servers. I’m not trolling or whatever the proper word for it. It’s not sarcasm either. I must be missing something, I guess. What is the reason? Especially if you’re not paying for it. But if you’re paying for it, I’m still curious.

  • It was like that when I got here. The servers at my work were all Ubuntu, so that's what I keep using. And if the servers are Ubuntu, I'll use that on my machine too.

Should we also talk about the snaps when trying to install package in Docker image (such as chromium-browser)?

  • I keep Snap disabled on my systems:

    cat /etc/apt/preferences.d/nosnap.pref

    Package: snapd Pin: release a=* Pin-Priority: -10

This turnaround time is appalling, especially given that Debian shipped a fix weeks ago. Poor show, Canonical.

OpenBSD got a recent GeFS (COW FS, but far lighter than BTRFS and not to mention ZFS) update, I wish 8.1 or 8.2 had it stabilized, because the issues with FFSv2 would end in the spot and maybe even steal some server machines to GNU/Linux.

From the same company that demands high school transcripts and club affiliations for engineers 20+ years out of high school.

Creepy as hell company. Had a good free Linux distro, but it's not that good anymore. It's coasting on inertia these days.

There seems to be something off about this post. One hour in and hundreds of comments.

Either this was used to pop something big, or this is a jia tan situation going down.

I thought there was a flamebait automation that was prevent this sort of velocity (unless overridden)

  • or maybe, just maybe, entertain for a second that upstream (linux kernel) shipped the original patch commit on October 1st with rollout to mainline on October 9th and disclosure on October 15th.

    People with affected systems have been waiting ever since for canonical to ship ... something, anything. Or maybe communicate the blockers. Crickets, though.

    It gets all the more egregious if you're a paying customer for Ubuntu Pro (which thank god, our company is not).

    It is absolutely taking the proberbial piss when you put it into context of their bold shiny new ambitions posted on September 23rd on their official blog (https://canonical.com/blog/accelerating-delivery-of-cve-fixe...) ... failing every single listed requirement in that announcement, now 14+ days, after initial CVE disclosure.

    No need for a tin-foil hat here at all. Ubuntu has a large installbase. Part of which hosts servers. And if I had to take a wild guess that userbase is about to shrink dramatically going forward.

    • People panicked about the issue can either apply a quick IPTables mitigation or install the kernel Ubuntu hasn't released to production yet. It's annoying that Canonical is late, but it's not the end of the world either.

      Unlike Arch or even Debian, Canonical has dozens of kernels to test and verify. The downside of supporting your software for ten years across multiple chipsets and even offering in-between kernel updates is that you need to test and maintain a shitload of kernels. Testing all of those takes time.

      I hope they do a write-up about what went wrong here but all the big companies were weeks late to the party. My guess is that some of the patches were causing issues when backported, or Red Hat would've released updates much sooner as well.

Maybe they got a bribe from some intelligence agency to leave it open a little longer.

I also ran into this problem. But it's possible to install an untested Linux kernel, and that fully solves the problem. As for Ubuntu — yes, it's terrible. Fortunately, there's a workaround.

A colleague once told me not to use Ubuntu in production. I was too busy/lazy to research why. That was ten years ago. I'm glad I procrastinated in my research and just used Debian all these years.

  • There are a lot of Ubuntu boxen in production out there. It is basically the default for Linux VMs in Azure, the UX sort of pushes you that way unless you have a particular preference otherwise. I do have a preference, for Debian which I've used at home for many years, but in DayJob Unbuntu is close enough and seems to make others more comfortable (in part due to the impression some have that it is better supported in Azure). I'm surprised MS aren't nagging Ubuntu to pull their finger out for this reason (maybe that are, behind the scenes, but if so it isn't working).

These recent burst of major security issues really have shown that paid security updates from the likes of Ubuntu and CloudLinux really aren't worth the paper they're written on.

Debian is, in every way that I know, superior to Ubuntu.

  - no snap nonsense where you can't turn off upgrades
  - stays close to upstream LTS kernels
  - does not carry around some ridiculous kernel patch set
  - no irritating adware on login

I switched after the aforementioned patch set broke containers and destroyed my server instance a couple years ago. Apparently nobody bothered to check containers before releasing the kernel.

  • Why are you lying so much?

    >no snap nonsense where you can't turn off upgrades

    You can disable AND uninstall snap entirely. You can also disable automatic update of the specific snaps you have installed.

    >stays close to upstream LTS kernels

    Same as Ubuntu, which uses 7.3 on its latest release as of today.

    >does not carry around some ridiculous kernel patch set

    Custom kernel patches for hardware compatibility is a very good thing, and why Ubuntu works on a lot of machines compared to other distros.

    >no irritating adware on login

    There is not a single ad on login, and even after. You are an ugly liar.

> distros run by volunteers (Debian, Arch, Alpine...) hve shipped the fix.

Well - Ubuntu sold out to marketing rather than engineering.

Happened to Google too. Compare Google Search to 10 or 15 years ago. Totally useless nowadays.

So nice to see people coming back around to Debian.

Listened to over a decade of people chirping about the new hotness and calling my Debian servers lame, old and busted. Well look at you now!

Everything that's built by a publicly traded company is built for shareholders, not for consumer. Switch before it became unswitchable or learn the hard way.

I cannot express how stable, secure and butter smooth Debian is for servers. I don't regret sticking with it for so long

I’ve always hated Ubuntu. I simply don’t understand the pitch as to why someone would use Ubuntu over just good ol fashion Debian. Better yet: FreeBSD.

Given that Ubuntu is downstream from Debian, I can't think of a single good reason why Ubuntu wouldn't just release Debian's patch.

I used to be a contributor to distros, but I found that Ubuntu simply has no method by which I can fix things and contribute them back.

Does no one remember Shuttleworth's underhanded deal with Amazon way back? That was treacherous enough to never look back.

I migrated all servers off Ubuntu as well due to this and slow PHP patching as well. Now running a mix of AWS Linux 2023 and Debian.

The bad news is that Canonical is slow to fix critical issues. The good news is that Canonical is full of people with exceptional SAT math scores.

In the current age of AI, open source means exploits can discovered directly through the code. The flip side is the patches can also be managed.

We are in that period between when software was good enough and when software is certified as secure by the writers.

The days of importing frameworks and libraries written by strangers is over. I would say the entire industry is not prepared at this moment for the unpatchable event where the only solution is to power off or disconnect.

  • Don't expect closed source to protect you. LLMs are very happy to analyse binaries and decompile functions you need. It's barely harder to deal with software you don't have the source for. I did both security and reveng work with LLMs and they don't slow down.

I'm not finding a reference to CVE-2026-98432 on the stable updates mailing list or in changelogs for 7.2 series.

Switch to vanilla Debian. What I did, no real issues that weren't easy to fix. Rock solid still.

> Anthropic says it built a working exploit that gets root on a server. A total takeover.

No offense but Anthropic says that every time.

A hot take - agents with root access dynamically updating your system have crossed over the threshold of being more secure than not using them.

I still haven't done this for my servers with SOC2 compliance (for obvious reasons), but I've moved over my personal project servers to this pattern. They all run ubuntu and this CVE was fixed within 1hr of my agent seeing chatter on twitter about it.

Still in the testing phase of this pattern, but while I initially thought it'd be a terrible idea[1], I'm coming around to it more and more with the amount of major CVEs hitting.

[1] https://news.ycombinator.com/item?id=50221604

if only other OSes had the same CUDA support as Ubuntu. Now I know how solidworks users feel..

  • All other Linux distros have the same gpu drivers.

    And you can have an ubuntu userland setup and any package necessary to run cuda in mere seconds on any linux distro thanks to toolbox and distrobox.

Withholding security-critical open source contributions to collect subscriptions is really low.

Bye Ubuntu

  • That's not what's happening here though. The haven't provided any patches for pro subscribers either!

    • whatever, I switched, it's not interesting to me anymore what I need to do to receive security patches that are part of FOSS.

      They are just casually rent-seeking.

beyond the nft/iptables mitigations discussed codex plopped out a kernel livepatch for my ubuntu kernels in about twenty minutes. the functions are ftrace’able so no trampoline/splice shenanigans required.

How about WTF linux?

The TCP/IP stack has one of the most stable requirements bases of any component -- modern PCs can communicate with decades-old software and hardware, and the composition of layers design means the code can be easily tested, and is a great candidate for analysis via formal methods. And once you have a formally verified implementation, the stable requirements means you can make it safe and then leave it alone.

  • Pretty much every OS I can think of has had one of these vulnerabilities. Microsoft had a bad one not so long ago that affected IPv6 packets, not even at TCP level. Dedicated RTOS packages that run Mars rovers have had network-level code execution exploits.

    Network routing is complex enough from a management point of view, doing it fast and safely is very hard. Formal verification sounds nice, but the network stack is more than a dumb pipe.

    For bugs like this, I hope the addition of Rust to the kernel will lessen the UAF vectors, but I'm sure it'll be years before that happens. The binder folks did a safe rewrite and encountered downstream companies hooking kernel tracepoints for state determination, I can't even begin to guess what they'll do to the network stack and how that'll affect adoption.

Normal Ubuntu approach. Not news. I have personally got a bunch on 10+ year old bug tickets on Launchpad and only lately got a feedback like: "is this still relevant"?

Of course, if one hides a bug long enough it will eventually disappear or become irrelevant.

Yes, indeed, WTF Ubuntu?

We were using ZFS in prod a few years ago, and there was a one-line patch to fix data loss issues.

It took Ubuntu something like 6 months to “backport” it. I’m not at all surprised they are taking forever to patch a severity 11 wormable exploit.

Mildly disappointed, but not surprised. Anyway, the ZFS thing (and, before that, widespread systemd-related breakage of an old LTS) are why I don’t trust them in prod anymore.

I mean....insert Linux distro of any kind. Yes, hardware support is good, but most distros are otherwise pretty awful in many other regards now.

I have the same general feelings, but then I recall my years as an OSS developer and being abused by people who contributed absolutely nothing to my projects. Not money, not code, not documentation, not even grammar corrections. I'm sure anyone who's been involved with reasonably popular OSS can relate.

I am not contributing to Ubuntu in any way, and that puts it into perspective.

(I still directly contribute to OSS and release OSS projects, but absolutely refuse to engage with the least bit of hostility. Any of that is an insta-block.)

Edit: Whoah the downvotes and comments. I'm not saying that Ubuntu is doing well here. I'm trying to point out that a a vast percentage of the complainers are not paying customers, and maybe if they did pay, Ubuntu would have more incentive and resources to work more quickly.

  • People are paying money for Ubuntu, though. I suppose if only the free versions were unpatched we could consider the ethics and merits of who is allowed to complain about what, but when the paying customers are also being left out in the cold I don't think your argument has much merit.

    • Sure, and those people have a right to complain.

      But, imagine if the complaint vs paid ratio were more equal.

      Right now, the ratio is massively skewed towards complainers vs paid. (>99.9% I'd guess)

      1 reply →

I have fond memories of burning Ubuntu to a CD being my first introduction to Linux. I chose to preserve those cherished memories rather than sully them through actually using Ubuntu.

maybe once it comes out you will need to pay them to get the patch xD

I suppose this kind of stuff is why you will find some places who roll Debian in prod but almost never find Ubuntu?

on laptops etc. its less impwct because (i think) most people are sensible enough not to have all kinds of listeners open all the time?/(right guys??? ...RIGHT GUYS???)

dont forget it can also be used as LPE if its a local host listener. and LLMs can bake u a nice exploit for it too.

Go Debian or perhaps consider freeBSD or OpenBSD if your workloads permit. they are more feasible, and sensible by the day, not just trying to poop on Linux, its simply much more targeted for now, and because it moves faster, and thus is bigger, it will have more holes.

a lot of ball dropping all around lately in lots of incidents and CVE. stay safe out there!

I'll add that they were a day or two late to patch the brotli issue, other than Ubuntu Pro LTS, which was still "under consideration" or whatever they called it, for another few days to a week. https://ubuntu.com/security/CVE-2026-111497 Now it says it's fixed, but on my old server I'm still not getting the updates for whatever reason (maybe I have it set up wrong? I dunno.).

I hate to be the guy to complain about a free service (Ubuntu Pro is a source of revenue, but it's free for individuals) but if I knew this was actually was actually being offered I would (hopefully!) have switched off by now.

Having migrated out of Ubuntu since 2016 (when they made systemd mandatory), I can only marvel at my own prescience... ;-)

Ubuntu has always been worse-Debian, I've always said it, now I have the strongest evidence in my favor.

The fact that Ubuntu (still) hasn't patched this (despite the fact that I'm pretty sure Opus 5.5 could figure it out in a few minutes) is pathetic. And it's very annoying for me because I have two servers that I need to consider migrating off of it now because Ubuntu clearly doesn't care all that much about security vulnerabilities like this. Get your shit together, Canonical. We all know you can do way, way better than this.

Everyone is just using Ubuntu for free of charge for the most part. You get what you pay for.

On another note, you can probably easily install the Debian kernel onto your machine.

"But we need signed kernels!" Well, that's a big "I told you so" from the people that were against only a handful of distros being able to create signed kernels with MS derived keys like 15 years ago.

  • You get what you pay for? Honestly this is so very disrespectful of the work thousands of people have and continue to put into Free Software including all Linux distros (Ubuntu too) as well as other operating systems and software. Really really disrespectful.

  • Having to get the client into call just so they go and click authorisation for adding some signing keys on VMs (as it was in pre-boot stage) just to add some driver wasn't fun

    What an awful system

  • > Everyone is just using Ubuntu for free of charge for the most part. You get what you pay for.

    That ignores those paying for Ubuntu Pro. They are not getting what they paid for.

> Anthropic says it built a working exploit that gets root on a server. A total takeover.

Can we stop giving value to what is said? It's time to only accept PoC's or at least some documentation as proof.

The recent PHP vulnerability made this even more apparent. LLM's were panicking, but the server were fine...

> and I considered it the solid, no-drama LTS distro. Fuck that now.

There's been lots of drama on Ubuntu which OP either completely missed or ignored. Ubuntu has been getting worse for over a decade now.

Yes, this is a fuckup by Canonical

But it doesn't sound too hard to backport a patch from Debian to Ubuntu yourself.

So if it's a critical security concern to your company, open your laptop and get to work.

I mean.. how many people are using multipath on Ubuntu? This is a big issue for datacenter systems that are using fancy networking features that Ubuntu users probably aren't.

  • Go programs listening on TCP have multipath enabled.

    • So they do. Also they mention in the golang-announce bulletin that MPTCP might not even be required for exploitation, it's just that the PoC requires MPTCP.

      1 reply →

i would then give claude/codex full access, and ask it to do a temp patch, if they allow lol.

agreed what the fuck are they doing, i moved off all my homelab and pc's to debian/fedora a while back.

ontop of the bullshit ads you get the terminal for paying for theire premium bullshit

Honestly, I agree. I need to provision a new VPS for a personal site and I’m holding off until it’s resolved.

Not to mention however many production services teams I work with build and maintain that run on Ubuntu.

Ubuntu are dragging their feet and it’s not good enough. Nowhere near good enough.

Get it patched NOW!

And if you’re on here and you work for Ubuntu, then what the hell are you doing reading this when you should be shipping a patch?

Seriously: get on it, will you?

I suspect at this point that it’s a bunch of techno-bureaucrats at Canonical who are dogmatically sticking with their release cadence because artificial justifications. I have worked in big organizations where The Process, or The $place Way of Doing Things, has become so big that the bureaucracy takes on a life of its own and you end up having a whole team of people who just manage the process so that the people actually doing the work can maybe get something done.

I haven’t used Ubuntu for a few years now but I’m glad they’re getting this trial by fire now. This new era of software vulnerabilities is going to reduce the viability of a lot of smaller distros who more or less are entirely dependent on upstream for security and reliability. I sincerely wish the Ubuntu folks well but this is a sink or swim moment, and even if they sink it will be a net positive for Linux as a whole as weaker projects get picked off like the slowest antelope in the herd.

Calm down, man. I think Ubuntu is doing o.k. here. What is pretty bad that people cannot read advisories anymore and fix there machines, instead crying for their mama (in this case Ubuntu).

Use this firewall rule and you are fine - it blocks the tcp options negoation - and things remain working of course: ` nft add table ip cve_2026_98432 nft add chain ip cve_2026_98432 pre '{ type filter hook prerouting priority -300; }' nft add rule ip cve_2026_98432 pre meta l4proto tcp ip hdrlength gt 5 counter drop `

What difference does it make? Version N (TEH LATEST) is considered secure until it isn't and the same show repeats with version N+1 but we already know it's also compromised.

  • The obvious difference is that version N-1 has a known vulnerability that could potentially be exploited, and everyone now knows about it.

    • And the version N+1 has exploits only the hackers know so as long as the general public is oblivious it's "secure".

      Let's be clear the security vulns will never end and if you're running anything connected to the network eventually you'll get pwned.

Where is my cup to collect all these tears from people upset about free software not getting fixed fast enough?

I wonder what is slower, these people pulling out a credit to pay something or ubuntu fixing their issue?

  • Probably right next to your reading glasses, my dude.

    Maybe grab those first, though.

    • They are on my face. It's how I read a blog post and comments of people who are complaining that free software isn't being updated fast enough for them.

      WTF Ubuntu! I'm not paying you for updates... so where the fuck are my updates bro?!

      1 reply →

"The free operating system that I use is not giving me enterprise level security updates"

I believe you can contribute to Ubuntu's source code right? Why don't you fix the issue then?

  • This doesn't work in practice. That's not really how OSS works; it's a naive interpretation. I can go into details if you'd like, but first: Have you taken this approach before? What were the results? I find it usually ends up in discussions/arguments with the owners, and it doesn't get merged. And I see the other side too; reviewing PRs is a burden, and the submitters often will fix their own problem, while introducing complexity or problems elsewhere. Also, it's generally MUCH easier for a maintainer/owner to update software than a rando who wants a bug fixed.

    • I fix it for myself, share it upstream, and have no fucks to give if the gatekeepers review it, reject it, merge it, or belch any purity bullshit in between.

      The beauty of OSS is that you don't need permission from anyone to modify the code to your own needs.

      3 replies →

  • > "The free operating system that I use is not giving me enterprise level security updates"

    Canonical absolutely is marketing enterprise security updates (at least for those who pay). I don't see this in the paid ESM updates channel yet either?

  • Their main point is that Canonical do in fact charge for security updates (they charge some companies for support), and yet are not providing them.

  • From the article:

    > Oh and btw, distros run by volunteers (Debian, Arch, Alpine...) hve shipped the fix. Meanwhile Ubuntu, made by a company that sells security subscriptions, hasn't. This is true as of 2026-11-02 14:48 UTC.

  • Ubuntu is one of the larger companies in the OS space and advertises themselves as providing long term support with rapid security fixes. AFAIK they haven't released a fix for their paying customers either. If they were complaning about arch or debian then I think you would have a strong point, when those distros have fast fixes but ubuntu doesn't I'm not so sure they that criticism of ubuntu is unwarranted.

    (Also, ubuntu already has the fix. What they're dragging their feet on is releasing the updated version. I don't think anyone outside ubuntu can help with that process)

  • Getting commit rights for kernel to "just fix the issue" in a corporate led dev project.

    Let's see you do it.

    • Probably depends on the company. Plenty love to publish useless blog posts about how “We, a SaaS company that produces React components, fixed a vulnerability in Ubuntu Kernel” because we’re involved in all of our tech stack like that. Linux kernel, node and react is our stack and we take ownership of it seriously dawg.

  • Two weeks late is hardly “enterprise level”

    If they don’t have the resources to handle this, they should be recruiting more help from their community

  • The most famous not-free-as-in-beer OS that specifically marks enterprise as their target market actually only fixed this yesterday... whatever you may want to take from that.

  • Ubuntu is not a small open source project ran by maintainers, Canonical is a full fledged b2b company with 600+ employees.

  • Canonical ltd is a multinational tech company with hundreds of millions of dollars in revenue from enterprise contracts

you mean to say you didnt review the codebase before putting it in production? you get what you pay for