OpenSSH 10.6p2 has been released with a workaround for a critical vulnerability.

https://openssh.com/releasenotes.html#10.6p2

If you operate a Linux system that uses musl libc without PAM (Alpine Linux is one example) then stop reading and set PasswordAuthentication=no or disable SSH for these systems IMMEDIATELY.

This vulnerability does not exist on non-Linux systems, Linux/glibc systems and Linux systems that use PAM for password authentication.

We consider the root cause of this bug to be outside OpenSSH itself, but we're in a good position to deliver a mitigation quickly.

We are making this release as fast as possible (we learned of the problem yesterday) because we have recently observed multiple cases of rapid bug rediscovery by AI agents, sometimes within hours, and so now consider long embargo periods to be a dangerous practice that primarily benefits attackers.

Thanks for Özgün Kültekin of Wakefield (wakefield.co) for reporting this problem to us and for the Alpine Linux developers for making an updated release available at very short notice.

@corbet Isn't this just trolling? I think "Mandalic Resonance" nails it.

For the past three years, Linux'n'Beer has been bringing people together in Zurich for a relaxed evening of conversations about Linux, the kernel, open source and whatever else comes up over a beer.

We are meeting again on Friday, 23 October at 7:30pm at Kennedy's Irish Pub.

If you happen to be around, feel free to drop by, have a pint and join the conversation.

I enjoy visit to Lviv in Ukraine, awesome food, even better craft beer, amazing friends. Only f*#*g Shaheds from Russia targeting civilian infrastructure are ruining the ambience.

We made it! 🚗💨 Switzerland ➡️ Ukraine, Lviv.

It was a long drive, but every single kilometer was worth it. Yesterday, we officially handed over our car to the Ukrainian defenders. The war demands an immense amount of resources, and dependable 4x4s, cars, and vans are constantly needed to keep defenders moving and save lives.

Now our beloved car has a new home and a noble mission. Freedom isn't free - thank you to the defenders who pay the price for it every single day for a sovereign Ukraine. 🇺🇦

If you have a vehicle to spare or want to support frontline mobility, let us know and we'll tell you how.

#CarForUkraine #ConvoyToUkraine #HelpUkraine #SwissWithUkraine #SlavaUkraini

@monsieuricon You can hit many funny moments, which might be fun itself :). There are several same sounding words with very different meaning. I personally enjoy the smeszne odpady (смішні відходи).

@geert https://sched.co/2RaWR ? Looks interesting and also relevant to Qualcomm, but I don't think they will let me in unfortunately. I'll check the recording once they publish it.

October is coming which means Linux Plumbers Conference 2026 in Prague, where I am running Devicetree Microconference track (6th of Oct). There will be talks about:

- Current progress with OF_UPSTREAM (@superna9999),
- Status of getting DT bindings compliance (me),
- Combining ACPI with Devicetree because the more firmware the merrier (Srinivas Kandagatla),
- Upstreaming your DTS faster than maintainers can review (Amit Kucheria),
- The never-ending saga of hot-pluggable extension boards (Hervé Codina),
- Another never-ending sagas of managing multiple boards with overlays (Doug Anderson, Hans de Goede and Agathe Porte).


Full schedule:
https://lpc.events/event/20/sessions/252/#20261006

Don't hesitate to grab me in the hallway track if you have some questions, e.g. why I still did not review your patch :), or just want to get a selfie with me (yes, it does happen, I am not making it up!). This year I am not attending the co-located ELCE, so only chance to catch up is LPC. See you in Prague!

@bagder I do agree. And if by any case you accept some LLM code to your project (piece looked reasonably) and then you want to have some joy to change something, extend, fine-tune, develop nice piece of good work you hit a wall - the code is not easy to actually follow and understand from design point. Of course the true mistake was in the beginning by accepting that contribution which was looking human-enough. I too believe there is much less now (I would not call it "no fun anymore" but we are getting there) and I was doing all that for fun.

The guy who shut down the Strait of Hormuz is telling Ukraine to halt strikes on Russian diesel fuel because it's causing shortages.

We are living in Idiocracy.

@corbet @alrj And in Geneve they spent quite amount of bucks for Large Hash Collider... :)

Next Open Source Summit or LPC could be in Canada, though. That's a Great Country. I would go to.

Some moron is running out of water bodies to rename after his ego. There was a gulf, now a lake. So I guess there is gonna be a river, sea and ocean soon? I'm happily avoiding all technical conferences as a speaker in a country ruled by said moron.

@EonBlue This gets you closer to supporting every Linux distro on this newer hardware, so of course including PostmarketOS. I don't really care about Android, but it benefits from it as well.

@fabrice Lack of public hardware access changes nothing in the review - you can still review everything the same way. And testing honestly also does not change much, since even after public announcement not many upstream developers have access to hardware to provide tests. IOW, testing would not differ if patch is released post announcement. Unless of course you mean years post, but that defeats any purpose of upstream (like is for 90% of other SoC vendors...).

I missed actually important milestone in July 2025 - first Linux kernel patches for Snapdragon X2 Elite SoC (next compute flagship model) were posted 2 months before public announcement:
https://lore.kernel.org/all/20250716151535.4054172-1-pankaj.patil@oss.qualcomm.com/

If someone asked me 5 years ago, I would not believe that I could produce such a statement about major SoC vendor:
https://lore.kernel.org/all/2509536d-cdec-448d-bf20-80d2b3d6728a@kernel.org/

Qualcomm and Linaro were upstreaming before significant amount of code to the Linux kernel for supporting their SoCs , but around 2021-2022 things changed significantly. Just to recap major milestones of:

2022 November: One day after public announcement of new Snapdragon 8 Gen 2 flagship SoC (SM8550), Qualcomm Landing Team in Linaro posted basic support for it:
https://lore.kernel.org/all/20221116103146.2556846-1-abel.vesa@linaro.org/

2023 October: One day after public announcement of next flagship Snapdragon 8 Gen 3 (SM8650), same team posts almost full (not basic!) support for it:
https://lore.kernel.org/all/20231025-topic-sm8650-upstream-dt-v1-0-a821712af62f@linaro.org/

2024 October: One day after public announcement of next flagship Snapdragon 8 Elite (SM8750), Linaro and Qualcomm team posts comprehensive support for it:
https://lore.kernel.org/all/20241021232114.2636083-1-quic_molvera@quicinc.com/

2025 September: Same day of public announcement of Snapdragon 8 Elite Gen 5 (Kaanapali), Qualcomm posts comprehensive support for it:
https://lore.kernel.org/all/20250924-knp-dts-v1-0-3fdbc4b9e1b1@oss.qualcomm.com/

Now things changed:

2026 March and from now on: Qualcomm posts patches for unannounced SoC yet, getting way ahead, for example:
Hawi: https://lore.kernel.org/all/20260330-clk-hawi-v1-0-c2a663e1d35b@oss.qualcomm.com/
Maili: https://lore.kernel.org/all/20260522-maili-pinctrl-v1-0-0a6636f5c277@oss.qualcomm.com/
(I don't know which models are these, what I know is they are not yet announced)

And this list above does not include upstreaming of many other models from different segments.

People really missed how big transformation Qualcomm did in upstream Linux kernel involvement.

their real worry is that the Ukrainians will find a way to improve the Patriot and then produce them at scale faster and for much less money than what the existing production lines in the U.S. could do

Yes, read this again.

Linux kernel Devicetree sources:

With my recent patches entire ARM, arm64 (except Broadcom Stingray and Apple) and RISC-V DTS files pass the dt-check-style linter, in default relaxed mode, so any new DTS is expected to not introduce new warnings.

IOW, in your contributions be sure that new DTS is dt-check-style warning-free.

I am working on fixing false positives for the strict mode and have some successes, but that is not yet ready.

Linux needs more maintainers. Myself must be overloaded, and heading for a burn-out:
$ git log --oneline MAINTAINERS | grep -i myself | head -3
51f449308506269e MAINTAINERS: make myself the maintainer of the Qualcomm QCE driver
12933e2bc5e07e15 MAINTAINERS: dmaengine/ti: Remove myself and add Vignesh as maintainer
4452b868d669fbf6 MAINTAINERS: Add myself as SCD30 maintainer
$ git log --oneline MAINTAINERS | grep -i myself | wc -l
348