Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. So CopyFail CVE-2026-31431 is a thing.

So CopyFail CVE-2026-31431 is a thing.

Scheduled Pinned Locked Moved Uncategorized
174 Posts 63 Posters 14 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • icing@chaos.socialI icing@chaos.social

    @uecker

    I think I should be the only one on that list. I‘ll then notify the right people who can demonstrate their worthiness.😌

    Wait! That‘s already anthropic‘s business idea. Damn.

    @gregkh

    uecker@mastodon.socialU This user is from outside of this forum
    uecker@mastodon.socialU This user is from outside of this forum
    uecker@mastodon.social
    wrote last edited by
    #164

    @icing @gregkh Would you consider Debian, arch, gentoo, Redhat, Ubuntu to be worthy?

    icing@chaos.socialI gregkh@social.kernel.orgG mormund@mastodon.socialM 3 Replies Last reply
    0
    • uecker@mastodon.socialU uecker@mastodon.social

      @icing @gregkh Would you consider Debian, arch, gentoo, Redhat, Ubuntu to be worthy?

      icing@chaos.socialI This user is from outside of this forum
      icing@chaos.socialI This user is from outside of this forum
      icing@chaos.social
      wrote last edited by
      #165

      @uecker

      You are a troll, Mr Uecker.

      @gregkh

      uecker@mastodon.socialU 1 Reply Last reply
      0
      • icing@chaos.socialI icing@chaos.social

        @uecker

        You are a troll, Mr Uecker.

        @gregkh

        uecker@mastodon.socialU This user is from outside of this forum
        uecker@mastodon.socialU This user is from outside of this forum
        uecker@mastodon.social
        wrote last edited by
        #166

        @icing @gregkh Sorry about that, but I find the "nothing could be done" and "responsible disclosure" is dead arguments fairly weak and I do not think that pointing this out is trolling. But let's stop here.

        1 Reply Last reply
        0
        • uecker@mastodon.socialU uecker@mastodon.social

          @icing @gregkh Would you consider Debian, arch, gentoo, Redhat, Ubuntu to be worthy?

          gregkh@social.kernel.orgG This user is from outside of this forum
          gregkh@social.kernel.orgG This user is from outside of this forum
          gregkh@social.kernel.org
          wrote last edited by
          #167
          @uecker @icing As is pointed, out, this is just a troll, but seriously, "worthy" isn't the issue. Again, you can not have one group "in" and one "out" without real reasons why anyone is "out".

          And again, my point remains, "All early release lists leak like a sieve, otherwise why does your government allow it to exist."
          uecker@mastodon.socialU 1 Reply Last reply
          0
          • uecker@mastodon.socialU uecker@mastodon.social

            @icing @gregkh Would you consider Debian, arch, gentoo, Redhat, Ubuntu to be worthy?

            mormund@mastodon.socialM This user is from outside of this forum
            mormund@mastodon.socialM This user is from outside of this forum
            mormund@mastodon.social
            wrote last edited by
            #168

            @uecker In case you are sincere: Is Hannah Montana Linux trustworthy? You also forgot Alpine Linux, Suse and and and and in your list, all of which are "serious" distros. What about Android? They run on billions of devices. But they won't patch anyways. Do they get to be in the club? If you inform all of them you might as well inform everyone.

            uecker@mastodon.socialU 1 Reply Last reply
            0
            • gregkh@social.kernel.orgG gregkh@social.kernel.org
              @uecker @icing As is pointed, out, this is just a troll, but seriously, "worthy" isn't the issue. Again, you can not have one group "in" and one "out" without real reasons why anyone is "out".

              And again, my point remains, "All early release lists leak like a sieve, otherwise why does your government allow it to exist."
              uecker@mastodon.socialU This user is from outside of this forum
              uecker@mastodon.socialU This user is from outside of this forum
              uecker@mastodon.social
              wrote last edited by
              #169

              @gregkh @icing I think the hostility "just a troll" is not necessary.

              1 Reply Last reply
              0
              • mormund@mastodon.socialM mormund@mastodon.social

                @uecker In case you are sincere: Is Hannah Montana Linux trustworthy? You also forgot Alpine Linux, Suse and and and and in your list, all of which are "serious" distros. What about Android? They run on billions of devices. But they won't patch anyways. Do they get to be in the club? If you inform all of them you might as well inform everyone.

                uecker@mastodon.socialU This user is from outside of this forum
                uecker@mastodon.socialU This user is from outside of this forum
                uecker@mastodon.social
                wrote last edited by
                #170

                @mormund Sure some of them would seem trustworthy. It might very well be impossible to create a perfect rule about who should or should not be on such a list. But this does not mean that one could not create some reasonable criteria and do a best effort. I disagree with "if you inform some of them you might as well inform everyone" Why should this be the case?

                1 Reply Last reply
                0
                • wdormann@infosec.exchangeW wdormann@infosec.exchange

                  What went wrong with this case?

                  Theori appear to have only contacted the linux kernel devs with the vulnerability, as opposed to going the usual CVD route that includes all of the major Linux distros.

                  Why is this a problem? Since the linux kernel became a CNA, there has been a flood of CVEs for the Linux kernel. The Linux kernel devs' arguments is that any given kernel flaw could presumably be leveraged to behave as a vulnerability, and it's not worth their time to determine "vulnerability" or "not a vulnerability". Everything gets a CVE.

                  Now the case with copy.fail? It was indeed reported to the kernel devs. And it got a CVE. A single CVE buried in flood of all of the Linux kernel CVEs.

                  And it appears that every distro on the planet was blindsided by this proven-exploitable vulnerability because they were not given any warning. Or even any suggestion to pick this single CVE out of the sea of Linux kernel CVEs as worth cherry picking.

                  Much to the chagrin of the Linux devs, RHEL doesn't use up-to-date Linux kernels. They cherry pick CVEs to backport to their chosen kernel version. (e.g. the latest and greates RHEL 10.1 uses 6.12.0, which was released November 17 2024). And in this world where bad actors like Theori don't involve vendors in vulnerability coordination, and just about every Linux kernel bug gets a CVE, this workflow fails. Hard.

                  Good times...

                  lioh@social.anoxinon.deL This user is from outside of this forum
                  lioh@social.anoxinon.deL This user is from outside of this forum
                  lioh@social.anoxinon.de
                  wrote last edited by
                  #171

                  @wdormann as Greg has pointed out clearly, it is not the responsibility of the Kernel Security team to inform any distro. The funny thing is that Theori, instead of doing that, claims it is not possible anymore and that any distro should instead use (their?) AI tools to spot critical CVEs for the Linux Kernel. This is just a big marketing fuckup.

                  wdormann@infosec.exchangeW 1 Reply Last reply
                  0
                  • wdormann@infosec.exchangeW wdormann@infosec.exchange

                    What went wrong with this case?

                    Theori appear to have only contacted the linux kernel devs with the vulnerability, as opposed to going the usual CVD route that includes all of the major Linux distros.

                    Why is this a problem? Since the linux kernel became a CNA, there has been a flood of CVEs for the Linux kernel. The Linux kernel devs' arguments is that any given kernel flaw could presumably be leveraged to behave as a vulnerability, and it's not worth their time to determine "vulnerability" or "not a vulnerability". Everything gets a CVE.

                    Now the case with copy.fail? It was indeed reported to the kernel devs. And it got a CVE. A single CVE buried in flood of all of the Linux kernel CVEs.

                    And it appears that every distro on the planet was blindsided by this proven-exploitable vulnerability because they were not given any warning. Or even any suggestion to pick this single CVE out of the sea of Linux kernel CVEs as worth cherry picking.

                    Much to the chagrin of the Linux devs, RHEL doesn't use up-to-date Linux kernels. They cherry pick CVEs to backport to their chosen kernel version. (e.g. the latest and greates RHEL 10.1 uses 6.12.0, which was released November 17 2024). And in this world where bad actors like Theori don't involve vendors in vulnerability coordination, and just about every Linux kernel bug gets a CVE, this workflow fails. Hard.

                    Good times...

                    lioh@social.anoxinon.deL This user is from outside of this forum
                    lioh@social.anoxinon.deL This user is from outside of this forum
                    lioh@social.anoxinon.de
                    wrote last edited by
                    #172

                    @wdormann as Greg has pointed out clearly, it is not the responsibility of the Kernel Security team to inform any distro. The funny thing is that Theori, instead of doing that, claims it is not possible anymore and that any distro should instead use (their?) AI tools to spot critical CVEs for the Linux Kernel. This is just a big marketing trick.

                    1 Reply Last reply
                    0
                    • lioh@social.anoxinon.deL lioh@social.anoxinon.de

                      @wdormann as Greg has pointed out clearly, it is not the responsibility of the Kernel Security team to inform any distro. The funny thing is that Theori, instead of doing that, claims it is not possible anymore and that any distro should instead use (their?) AI tools to spot critical CVEs for the Linux Kernel. This is just a big marketing fuckup.

                      wdormann@infosec.exchangeW This user is from outside of this forum
                      wdormann@infosec.exchangeW This user is from outside of this forum
                      wdormann@infosec.exchange
                      wrote last edited by
                      #173

                      @Lioh
                      Vulnerability coordination was clearly only an afterthought.

                      The copy.fail website included screen recordings of 4 Linux distributions being compromised. And at publication time had the audacity to state:

                      Most major distributions are shipping the fix now.

                      Narrator: No distribution had prepared a fix at publication time, as no distribution was even aware of the vulnerability.

                      The irony in all of this: Brian Pak (the Theori CEO) got his infosec fame as part of the PPP group at CMU, which is the home of the CERT/CC.
                      Bonus irony: Brian applied at the CERT/CC in 2011 for a position on the team that does vulnerability coordination when I was there.

                      So to spin things as The old model simply doesn’t scale anymore and our best intention was always to improve Linux security is simply laughable. The goal was a successful publicity stunt. Zero F's were given to the Linux users of the planet.

                      Link Preview ImageLink Preview ImageLink Preview Image
                      1 Reply Last reply
                      0
                      • wdormann@infosec.exchangeW wdormann@infosec.exchange

                        So CopyFail CVE-2026-31431 is a thing.

                        Link Preview Image
                        wagenseil@infosec.exchangeW This user is from outside of this forum
                        wagenseil@infosec.exchangeW This user is from outside of this forum
                        wagenseil@infosec.exchange
                        wrote last edited by
                        #174

                        @wdormann guess it's time to finally update to the latest then

                        1 Reply Last reply
                        1
                        0
                        Reply
                        • Reply as topic
                        Log in to reply
                        • Oldest to Newest
                        • Newest to Oldest
                        • Most Votes


                        • Login

                        • Login or register to search.
                        • First post
                          Last post
                        0
                        • Categories
                        • Recent
                        • Tags
                        • Popular
                        • World
                        • Users
                        • Groups