63 Followers
231 Following
211 Posts
vulns | radio | amateur astrophotography

@jwildeboer @darkcyberman @larsmb @dazo
How many Linux kernel CVEs were there in 2025? 5500?

How does Red Hat determine which of these to cherry pick as worth backporting?

@sj chaotic alignment was lacking so I created a chart

While this vulnerability seems to be discovered using AI ("Xint Code"), I have to assume that they also let the AI decide how to do the vulnerability coordination as well.

  • major builds are out as of this writing ๐Ÿ˜‚

    No distros have official updates for CVE-2026-31431. Fedora 42 and newer have updates, but no official advisory or acknowledgement of CVE-2026-31431. So with them it's unclear if it's even intentional. Red Hat, Ubuntu, Amazon Linux, and Suse all have advisories as of now, but NO updates.

  • disable the algif_aead module as a mitigation. ๐Ÿ˜‚

    Bespoke distros like RHEL don't use a module, it's compiled into the kernel.

I can't figure out what the Xint Code angle is with this copyfail stuff. On one hand, yes, it is a true vulnerability that affects a LOT of Linux distros available. And they did submit the bug for fixing to the upstream kernel people.

BUT the CVE has only existed for a week. And NONE of the distros IN THEIR ADVISORY had updates available at the time that they pulled the trigger for publication of the shiny copy.fail website.

I struggle to think of how this even happens. In all my years of infosec, you're either on board with doing CVD (e.g. coordinating with the former CERT/CC) or you're not (dropping 0day). But this all fits bizarrely in the middle. The publication gives the guise that they did the right thing, (and please use our AI services). But at the same time, they clearly chose to release the vulnerability details and functional exploit before any distro had the ability to properly do anything about it.

Either these Xint Code (Theori) people have a hidden agenda or ulterior motive that we aren't aware of yet. Or they're just really bad at coordinated vulnerability disclosure. You pick.

Tired of reversing the same libc for the 100th time? ๐Ÿ‘€

Meet SightHouse, our open-source tool that automatically detects third-party library functions in binaries.
High-confidence function mapping. Works with any disassembler. By @madsquirrel & Sami.

๐Ÿ”— https://blog.quarkslab.com/sighthouse-automated-function-identification.html

Watching the livestream of the Artemis II launch, I just witnessed one of the astronauts type in the password on their tablet while sitting in the capsule on camera.

#ArtemisII #Artemis #Artemis2 #NASA #InfoSec #cybersecurity #OpSec #Privacy #SpaceExploration

Weโ€™re spending an enormous amount of time, money, and effort, requiring vision and courage, to do something big where the objective isnโ€™t to kill anyone or conquer anything, but just to perhaps learn some interesting things about the universe in which we live.

Maybe some politicians get some bragging rights.

Iโ€™m OK with that, even if I donโ€™t care for the politicians.

"but watchTowr, why did this take AWS so long?"
I'm glad I got to enjoy gaming in the era before you needed a $7,000 rig to redraw frames and generate slop frames to hit 62 fps in a AAA game.
We won the war with the Gorn on the first day basically, but it will probably last 6-8 weeks. They should just surrender and absolutely NOT MINE THE WORMHOLE!! That would be a BIG MISTAKE! #StarTrek #Sisko197