Dirty Frag: getting root after AF_ALG was blocked and public poc failed
A recent exploit known as Dirty Frag allowed a user to gain root access on a university server despite security measures. The exploit took advantage of a flaw in the kernel's crypto implementation, which was not fully mitigated by blocking the AF_ALG interface. The user successfully reported the vulnerability, leading to a prompt patch by the system administrators.
- ▪The exploit targeted a shared login server at IIT Delhi, running a relatively new version of Ubuntu.
- ▪Despite the server's security measures, the user was able to exploit a flaw in the kernel's crypto implementation.
- ▪The user utilized a feedback loop with a tool called DeepSeek-V4-Flash to successfully gain root access.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Shauryaa |
| Canonical URL | https://shauryaa.dev/blog/dirtyfrag-afalg-bypass-nscd-fix/ |
| Publication time | Fri, 29 May 2026 01:10:05 +0000 |
| Retrieval time | 2026-05-29T01:29:39.549Z |
| Last seen | 2026-05-29T01:29:39.549Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 94Bya6FnJwZa |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
May 29, 2026 dirty frag field notes: from a patched server that was "safe" a public Dirty Frag PoC failed, so the server looked safe. a cheap DeepSeek-V4-Flash feedback loop found the missed path -> fcrypt mismatch, nscd cache, and root in ~90 minutes. the short version i got root on my university's shared login server. not because the sysadmins were asleep or because the box was some ancient forgotten machine. they were actually fast. they had read the CVE writeups, blocked the recommended kernel crypto interface, disabled unprivileged user namespaces, tested the public PoC, watched it fail, and moved on. reasonable response tbh. the problem is that public PoCs are not truth oracles. they only tell you one thing: this exact code path, as written, did not work on this exact run.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Shauryaa.
Discussion
0 commentsMore from Shauryaa
