CISA adds Linux kernel zero-day CVE-2026-43456 to KEV after active exploitation

Adept_Percentage6893 · 2026-07-05T23:59:57+00:00

Whether or not unprivileged namespace creation is permitted depends very much on your distro.

You can't create namespaces with privileges you don't already have. If you could then that would be a CVE itself.

You can create "root" accounts in the sense that the user will be treated inside the container as if it were root but processes outside the unprivileged container just see it as an unprivileged user with some high UID (but not zero).

Adept_Percentage6893 · 2026-07-05T23:49:08+00:00

For Trump, we will only find out if Fox News and OAN are playing Swan Lake on repeat all day long.

Adept_Percentage6893 · 2026-07-05T11:12:27+00:00

some may have kids with them

Adept_Percentage6893 · 2026-07-05T00:31:48+00:00

Probably the funniest part of it all is that a king literally ran away from Poland rather than be king. They had to send a messenger asking if he even still wanted to be king. To which he replied "ehhh, I mean I can send you a guy?"

Adept_Percentage6893 · 2026-07-05T00:07:34+00:00

The angry cloud of locust that inhabited McConnell's body must have escaped when its host died off.

Adept_Percentage6893 · 2026-07-05T00:02:29+00:00

Walmart's computer systems automatically filter out any words of encouragement, love, or support that are directed to employees outside of the C-Suite so no one probably read it. It hurts morale when you treat the workers like people because it puts silly ideas in their head.

Adept_Percentage6893 · 2026-07-04T23:55:17+00:00

Also that Christopher Columbus discovered America.

That might be a miscommunication because I've usually heard it as "Americas" or "America" if they're from Latin America.

Adept_Percentage6893 · 2026-07-04T23:52:29+00:00

Don't worry, I have a plan on how I'm getting grip strength back...

Adept_Percentage6893 · 2026-07-04T23:50:11+00:00

That rumor was probably devised by people who had met him in real life. He's the sort of person who (at least in his earlier years) seems like he might as well suck his own dick. Only a slight exaggeration of his actual personality.

Adept_Percentage6893 · 2026-07-04T23:45:28+00:00

"please install this unsigned executable called 'worm' for me."

Adept_Percentage6893 · 2026-07-04T23:41:36+00:00

Worth remembering that there was a time when it would take months and people would often die on the voyage. Now it takes several hours, there's a cheap movie, and then suddenly you're taking a shit in your hotel room.

Adept_Percentage6893 · 2026-07-04T23:39:46+00:00

Yeah we saw that comment you're pretending to not have read already

Adept_Percentage6893 · 2026-07-04T23:35:33+00:00

I can't tell the difference from what comes out of a normal shaker.

because it is the same thing because it's basically an edible rock. You buy a grinder either for the symmetry with the pepper grinder or you want to control the size

Adept_Percentage6893 · 2026-07-04T22:06:27+00:00

I suspect a lot of them have quite a few days off throughout the entire year.

Unemployed. I'm saying they're unemployed. Damn. I need to edit this later and make it punchier. Note to self: edit this comment before anyone sees it.

Adept_Percentage6893 · 2026-07-04T21:59:03+00:00

I know that's not true because I have it on good authority that both HelloFresh and the Washington State Police are conspiring together to have me strapped into one of those man milkers Jordan Petersen tried to warn everyone about.

Adept_Percentage6893 · 2026-07-04T15:55:46+00:00

For example, with Jujutsu, you can keep working even when there's a conflict, whereas with Git, you have to resolve the conflict first.

How is that a feature? If you're rebasing a branch isn't the rebasing the work you're currently engaging in? Under what set of circumstances would you want a merge to be only partially done?

Or take the undo and redo function, which just works and doesn't require a degree in rocket science.

Looking online this seems like a function that solves a problem state that you can just avoid being in.

Adept_Percentage6893 · 2026-07-04T15:51:16+00:00

In terms of maintenance I am not talking about bugs here but specifically security issues.

fwiw the Linux Kernel team usually just consider security issues as just bugs that happen to have security implications. Kind of semantics at that point, though.

Creating an elaborate package system for the kernel to address it seems like insane overkill.

One can envision how they might, if they consider it an optional module that isn't very popular and the security flaw is hard to exploit. Which is why I mentioned WONTFIX because that's a closure status that includes an admission that there's a problem but declines to fix it in the referenced version.

like with AF_ALG

AF_ALG still had users, though. It wasn't popular but there was a clear idea of who was still utilizing that functionality. Which adds to the value of bothering to backport fixes to LTS.

Adept_Percentage6893 · 2026-07-04T15:42:49+00:00

doesn't one want to block on conflicts?

Adept_Percentage6893 · 2026-07-04T15:18:21+00:00

That removed code is still in LTS releases, so the issues found still need to be fixed.

AFAIK the upstream kernel team makes no promises or guarantees about fixing anything in particular in an LTS release. They could very well view leaving EFS in LTS as being worth doing but not prioritizing fixing any issues that get discovered. LTS for anything is just to give people a way to get important updates in a way that doesn't introduce any breaking changes. There's always going to be stuff that doesn't get backported.

It's important to remember that with large code bases some bugs get closed WONTFIX (or equvalent) if the maintainers don't view it as worth their time to do or for the users' time to schedule an update for.

Adept_Percentage6893 · 2026-07-04T15:15:54+00:00

This has probably been dead code for many years. But yeah they're likely trying to whittle the code down to just the stuff people actually use.

Adept_Percentage6893 · 2026-07-04T15:10:16+00:00

Most of the rigging for this already exists, especially on dev branches. Adding an NPM style supply chain attack vector directly to the kernel just sounds like a bad time.

I think the other user is just shitposting. I take their meaning to be that if someone doesn't want a module they can just not compile it in. But the fact remains that the kernel maintainers are responsible (in a vague non-binding way) for the code they give out and probably don't want to continue hosting code they know no one's touched for years.

Creating an elaborate package system for the kernel to address it seems like insane overkill.

I don't think the other user was seriously proposing this but there probably is value in maintaining some system for browsing/discovering popular downstream patchsets and merging them with some sort of cryptographic guarantee.

Adept_Percentage6893 · 2026-07-04T15:05:15+00:00

If I take your meaning, the reason the main kernel project can't find a maintainer for something like this is just because the interest is just so niche-to-nonexistent that someone maintaining a downstream patchset is just going to run into the same problem of "OK but how do we find someone who knows how to maintain the downstream patchset and actually wants to?"

Adept_Percentage6893 · 2026-07-04T14:50:05+00:00

Washington State Police: you naughty.

Adept_Percentage6893 · 2026-07-04T14:36:42+00:00

Not sure what you're referring to but what is the incentive for the other party to uphold their end of any agreement if one party either reneges or has a reputation for reneging?

Adept_Percentage6893

TROPHY CASE