frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Residential proxies detected on White House network

https://layer3intel.com/blog/residential-proxies-white-house-network
575•Rasbora•4h ago•177 comments

Introducing Images 2.6

https://openai.com/index/introducing-images-2-6/
51•davidbarker•1h ago•31 comments

AI is forcing us to pay off 40 years of technical debt

https://spectrum.ieee.org/ai-in-cybersecurity-php2shell-vulnerability
1041•pseudolus•12h ago•623 comments

Local privilege escalation vulnerabilities in Linux

https://openai.com/index/a-thousand-fewer-paths-to-root/
44•dangelosaurus•1h ago•30 comments

Ripple-65B Preview: U.S. Open-Weight SOTA on Agentic Coding

https://www.ricursive.com/ripple
209•Philpax•5h ago•74 comments

Insects don't swarm at LED lights

https://www.birdsoutsidemywindow.org/2026/11/03/insects-dont-swarm-at-led-lights/
154•speckx•5h ago•91 comments

Kimi K3.1 Pro model weights are out

https://huggingface.co/moonshotai/Kimi-K3.1-Pro
352•abrarthought•9h ago•92 comments

Hacking the Xbox 360 Hypervisor Part 3: Bad Update Improvements

https://icode4.coffee/?p=1746
48•muricula•2h ago•2 comments

A new Go API for JSON

https://go.dev/blog/jsonv2
213•olexsmir•6h ago•91 comments

Qualcomm Cloud AI 100 Ultra – 150W AI Accelerator Card with 128GB at 548GB/s

https://www.qualcomm.com/data-center/products/cloud-ai-100-ultra
94•peter_d_sherman•4h ago•41 comments

Conductor is joining Meta

https://www.conductor.build/announcement
96•kenrose•6h ago•133 comments

Launch HN: Kino AI (YC S23) – AI media manager and video editor

68•lukeigel•7h ago•26 comments

Progress on provable inference for large language models

https://www.anthropic.com/research/provable-inference
171•ltononro•7h ago•83 comments

Nvidia RTX Spark encrypted firmware slows inference speed to 35% on Linux

https://www.mindstudio.ai/blog/linux-nvidia-rtx-spark-laptop
587•novaRom•16h ago•271 comments

Show HN: After a decade of reversing, I got co-op working in DOS Wing Commander

https://fireflyk64.github.io/wcmulti/
100•daniel_rh•5h ago•11 comments

Bf16 might be freezing your weight updates

https://lacuna.tiptreesystems.com/paper/bf16-might-be-freezing-your-weight-updates/art_487b1ed949...
8•martincsweiss•2d ago•2 comments

Guerrilla bike lanes: San Francisco makes illicit infrastructure permanent (2016)

https://99percentinvisible.org/article/guerrilla-bike-lanes-san-francisco-makes-illicit-infrastru...
248•zenincognito•9h ago•180 comments

Basically no one is using AI agents for their DoorDash orders

https://arstechnica.com/ai/2026/10/doordash-says-outside-ai-agents-have-only-led-to-hundreds-of-o...
60•PaulHoule•2d ago•87 comments

Is Curiosity Good for Us?

https://www.lrb.co.uk/the-paper/v48/n20/adam-phillips/is-curiosity-good-for-us
15•NaOH•1d ago•5 comments

OpenAI to acquire Pierre Computer Company

https://openai.com/index/openai-to-acquire-pierre/
170•itunpredictable•9h ago•55 comments

Show HN: Gauge – Open-Source CLI to recursively improve your docs

https://github.com/gauge-sh/gauge-cli
12•0x63_Problems•4h ago•3 comments

Ask HN: What's your current AI agentic setup?

99•eggbrain•10h ago•112 comments

Death Comes for XSLT

https://dbushell.com/2026/11/03/xslt-rip/
35•colejohnson66•3h ago•12 comments

A wave of plastic-free coffee pods and machines

https://www.cnn.com/2026/11/02/food/coffee-machine-plastic-free
39•thunderbong•9h ago•62 comments

Tencent Hy4

https://hy.tencent.ai/research/hy4
173•Philpax•10h ago•61 comments

Show HN: The DNA of DOOM – How code structure survives across 44 ports

https://squid-protocol.github.io/gitgalaxy/museum-of-code/doom-dna/
16•joe-esquibel•2d ago•10 comments

AMD expects to outsell Intel in Q4 for the first time in history

https://www.tomshardware.com/pc-components/cpus/amd-expects-to-outsell-intel-in-q4-for-the-first-...
451•rbanffy•9h ago•164 comments

Have I befriended a murderer?

https://longreads.com/2026/11/03/murder-friendship-doubt/
105•gmays•6h ago•57 comments

Show HN: I built a tool that prices a pre-built PC part by part

https://pcdealcheck.com/
92•adlep•9h ago•63 comments

Verification Is Not Knowledge: Science needs more than answers

https://blog.cosmos-institute.org/p/verification-is-not-knowledge
227•ersinesen•15h ago•130 comments
Open in hackernews

Local privilege escalation vulnerabilities in Linux

https://openai.com/index/a-thousand-fewer-paths-to-root/
39•dangelosaurus•1h ago

Comments

dangelosaurus•1h ago
This is my team’s work. I’m happy to try to answer questions or take questions back to the team.

And we're hiring! https://openai.com/careers/search/?q=cyber

BoppreH•1h ago
It's a bittersweet result, like finding asbestos in your house. I'd rather know than not, but I would much prefer not having it in the first place.

I understand this work was based on a dated snapshot. Will there be any continuous effort, scanning new PRs as they land, to prevent new weaknesses from being added?

ky1ebot1337•30m ago
(I am the author the pipeline, just created an account to answer some questions :D) My goal is to work towards a vuln-free Internet. What I observed is that stronger models can find many more vulnerabilities that weaker models cannot. If compute permits (there are other projects to secure besides Linux), I plan to scan Linux again with every newer generation of cyber models.
farisght•49m ago
I wish these blog posts included statistics on the categories of deficiencies that cause these vulnerabilities, and proposed measures to avoid them

A system that admits THOUSANDS of such vulnerabilities is certainly flawed in several fundamental aspects

jethro_tell•26m ago
It sounds like they can’t go through them all enough to have that data yet.
konaraddi•44m ago
As models get more advanced and generate an increasing throughput of increasingly higher quality results, how are you determining when to trust its results and when human review is needed on what?

E.g., 948 results is a high number to review in a timely manner unless your team is very large or spending several months combing through the results

EDIT: nvm i shouldve kept reading, answered

> At this scale, manually investigating every report is impractical for our research team. We therefore focused on validating findings that a) were reachable by a low-privileged user, b) required no special capabilities, and c) produced measurable evidence of memory corruption.

ahsillyme•18m ago
Thanks. I'm not a programmer so I can't understand what is happening in the kernel by looking at the changelog, so I'll ask: Are the problems remediated structurally so that nothing like it can occur in the future, rather than just patching it up? Are there "lessons learned" that are being applied and documented here (like, "this problem looks like it's shape transports to other subsystems as well, let's fix them all in a disciplined way")?
basilikum•5m ago
[delayed]
zahlman•50m ago
> We've developed an autonomous vulnerability discovery, exploitation, and patching pipeline. In one run with our cyber model, it validated and generated patches for 948 local privilege escalation vulnerabilities in Linux at an API cost of $1.2 million.

Imagine if open-source organizations other than the Linux Foundation (and Mozilla I guess) could throw $1.2M of API-rate LLM usage at security.

getcrunk•47m ago
> For the near and medium term, having access to a low-privileged account on an operating system, that isn’t up-to-date on its latest available patches should be considered functionally equivalent to root access for a well-resourced threat actor.

*buries head in sand*

*cries*

rubinlinux•28m ago
This has been true for DECADES.
basilikum•19m ago
Regular LPEs are not novel. The frequency has just increased a lot.
Plasmoid•41m ago
How did we get to the point where there are a thousand privilege escalation exploits in the kernel?

Is the kernel simply too complex to reason about? Is it an underlying flaw in the security model or language implementation?

Should we assume that all software is more compromised than the kernel?

antonvs•36m ago
> How did we get to the point where there are a thousand privilege escalation exploits in the kernel?

We developed AIs that can find them.

spartanatreyu•8m ago
> How did we get to the point where there are a thousand privilege escalation exploits in the kernel?

> > We developed AIs that can find them.

We could already find them before AI.

We already knew they were there, and we already knew how to prevent them in the first place.

See previous discussion: https://news.ycombinator.com/item?id=49705794

esseph•6m ago
[delayed]
p-e-w•29m ago
How can it be surprising that a software made from 40+ million lines of memory-unsafe code has hundreds of critical bugs?
hoppp•
nas•32m ago
I've always considered local escalations to be possible in Linux (i.e. having user access almost certainly means you can get root). However, 948 vulnerabilities is kind of shocking. Hopefully we are getting to the end of the part where it "gets worse before it gets better".
tamimio•30m ago
These are becoming more and more marketing materials than actual findings, because OAI probably hit the wall in making their models smarter (just like how google try to specialize their models in legal or whatever), but they need to remain relevant in the news. Sol 6.1 sucked so bad in reasoning that either it’s actually a bad model or users behind the scenes get degraded outcome while using all the resources for these marketing stunts. Stop, it’s embarrassing, make better models or be gone, at least we will get cheaper RAM to advance the development of open weights models.
hoppp•29m ago
Well at least they are doing public service while hacking the planet.
29m ago
There are always more left.
ChickeNES•9m ago
And memory safety doesn't prevent logic errors (or using 4 as a private key for that matter)
0xbadcafebee•23m ago
Funny how OpenBSD is "memory-unsafe" yet doesn't have these issues. Could it be that the programmer might have something to do with it?
esseph•7m ago
[delayed]
cyberax•7m ago
Is anyone spending millions of dollars on checking OpenBSD?

But it also got its share of use-after-free and OOB access vulnerabilities this year: https://feedly.com/cve/vendors/openbsd

icepush•7m ago
As an OpenBSD lover and frequent user I will tell you it does not support but a significant fraction of the hardware Linux does, and has many features that are reduced in functionality or just gone compared to Linux.

Is it bulletproof? Definitely! But you need the genius of Albert Einstein as well as the patience of Mother Theresa to actually use it in production.

bombcar•26m ago
The dirty secret is multi-user died in the 90s and privilege escalation has basically been considered table-stakes since then.
mikestylz•25m ago
> Should we assume that all software is more compromised than the kernel?

Absolutely, the front door has always been unlocked. We were previously protected by the economics of exploit detection favoring the developers, but now we have entered a new world.

The issues arise almost everywhere we look. It's frustrating because the user experience in edge systems has barely changed in the last fifteen years. We could have rode the advances in semiconductor manufacturing to embed more layers of protection such as CHERI while slightly slowing down the rate of performance improvements. Instead we have only marginally upgraded security and largely added features which the users scarcely notice.

I am hopeful about the long term prospects of formal verification, but having humans reviewing the proof statements and confirming they match our desired properties will take many years. Meanwhile, AI assisted hacking is an urgent issue. So we will have to delegate implementation, proof specification, and proof development to the AIs in the short term. Maybe that goes well, but who knows. Interesting times.

AnimalMuppet•17m ago
I recall reading that every IBM mainframe OS release had 1000 bugs in it. (This was in the 1970s/80s.) Sorry I can't supply a source, after 4-5 decades. It was probably an article in Datamation magazine.

Now, I don't know how many of those bugs were privilege escalations, or could be leveraged to be. I'm not sure that people tried to exploit in the same way back then (or, if they did, if they said anything publicly about the results). Still, even if the majority of those bugs were not exploitable, OSes were much smaller then.

So that's my conclusion of how we got here: We've always been here.

esseph•7m ago
[delayed]
asveikau•11m ago
For all of my time being aware of this industry, it has generally been understood that privilege escalation bugs are common. This has always been a thing. A lot of people say, commonly and for many years, that if your security depends on there not being privilege escalation bugs, you don't have security.
est31•9m ago
The kernel has the problem that basically every bug in it is also a security vulnerability. All software has bugs. Had Linux been written in Rust, and I strongly recommend a rewrite, it would still have bugs, and thus would still have vulnerabilities. But they'd be way less.