Kernel Linux · Public exploit code

Public exploit turns normal Linux users into root, fix unreleased

· 1 min read

Researcher Nad (Nadsec) published an exploit on 15 November on Mastodon for a flaw in assoc_array, kernel Linux code that tracks stored security keys. The researcher says the exploit turns a normal user into root; the flaw has no CVE, is considered currently unpatched, a fix has been committed but is not confirmed in any released kernel, and no one has independently confirmed the exploit works. Update the kernel once the fix lands in a released version.

WhatsApp LinkedIn X
HighVulnerabilityPublic exploit codeUnpatched

In 30 seconds

IntCyberDigest
Observed

A security researcher has published exploit code for a newly disclosed flaw in the Linux kernel. The bug sits in assoc_array, kernel code that keeps track of stored security keys, and it has no CVE identifier yet. A fix has been committed, but it is not confirmed in any released kernel.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list

Alleged

The researcher says the exploit turns a normal user account into root, the most powerful account on a Linux machine. That claim is the heart of the story, and so far it rests entirely on the researcher's word.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list

Observed

The exploit went public on Mastodon on 15 November under the name Nad (Nadsec), and no one has independently confirmed that it works.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list

What happened

Observed

On 15 November, a researcher posting as Nad (Nadsec) published an exploit on Mastodon for a flaw in the Linux kernel. The security news outlet IntCyberDigest picked up the find and relayed the details on X on 16 November.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list

Observed

According to that relay, the bug lives in assoc_array, the code the kernel uses to keep track of stored security keys, and no CVE has been assigned. The researcher describes the flaw as "currently unpatched". A fix has been committed, but it is not confirmed in any released kernel.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list

Why it matters

Inferred

If the root claim holds, this would be a local privilege escalation: someone who already has a normal user account on a machine, or malware running as that user, could take complete control of it. Public exploit code sharply lowers the effort for anyone trying.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list

Inferred

The timing compounds the concern as reported. With a fix committed but not confirmed in any released kernel, there may be a window where the flaw is public, the exploit is public, and no patched release exists to install.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source listIntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list

What to do

Inferred

The reporting points to one clear action: watch for the committed fix to land in an actual kernel release, then update as soon as your distribution ships it. Until that happens, the evidence says there is no released patch to apply.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list

Inferred

Treat the root claim as unverified for now. It comes from a single researcher, and nothing in the evidence shows independent confirmation, so calibrate urgency to that reality rather than assuming every Linux machine is exposed.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list

Confirmed and still uncertain

Observed

Known, per the reporting: the exploit was published on Mastodon on 15 November by Nad (Nadsec). The flaw sits in assoc_array code that tracks stored security keys. No CVE has been assigned, and a fix is committed but unconfirmed in any released kernel.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source listIntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list

Observed

Unknown: whether the exploit actually works, since no independent confirmation appears anywhere in the evidence. The reporting also does not say which kernel versions are affected, when the committed fix will reach a release, or whether a CVE is on the way.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source listIntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list

What people are saying

Alleged

The researcher, Nad (Nadsec), says the exploit turns a normal user into root and calls the flaw "currently unpatched". Those are the strongest claims in the story and they are the researcher's own.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list

Observed

IntCyberDigest, the outlet relaying the find, adds its own caution: no one has independently confirmed that the exploit works yet.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list

Evolution

Inferred

The chain visible in the evidence runs from a single Mastodon post on 15 November to amplification a day later. IntCyberDigest pushed the story on 16 November through X, and matching entries for its Telegram channel appear in the same batch, which suggests a coordinated relay across several channels rather than organic spread.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source listIntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source listt.met.me · rssOpen original sourceSee in source list

Reach

Observed

3 independent groups, 1 updates, and 15 engagements.

Technical detail

Observed

The flaw sits in assoc_array, the code the kernel uses to keep track of stored security keys. In plain terms, it is bookkeeping for the system that stores keys on a machine, the credentials the kernel holds rather than an application feature users touch directly.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list

Observed

On the patching front, the reporting says a fix has been committed, meaning it exists in kernel development code, but it is not confirmed in any released kernel, the versions people actually run. No CVE identifier has been assigned yet.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list

Sources and evidence

Observed

The substance in this batch comes from two IntCyberDigest posts on X, dated 16 November, which cite the researcher's Mastodon post as their source. The batch also holds RSS entries for the outlet's Telegram channel and newsletter, both arriving without body text.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source listIntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source listt.met.me · rssOpen original sourceSee in source list

Inferred

The primary source, the Mastodon post by Nad (Nadsec), is not included directly in the evidence. Everything about the exploit's behavior, the fix status, and the missing CVE rests on the digest's relay of that post, which is worth weighing when judging how solid the claims are.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list

Sources

  1. IntCyberDigestx.com · IntCyberDigest · x
  2. IntCyberDigestx.com · IntCyberDigest · x
  3. t.met.me · rss

Incidents like this, every morning

The ones that need action first, in a 3-minute read.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click

Get the next one tomorrow morning

One email a day with what changed, what to fix first and how.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click

Share it with your team

Whoever handles security with you should get it too.

LinkedIn X

Your colleague gets a confirmation request. Nothing is sent unless they confirm.

See all news

Read also

Before you go: get this every day

The HIFY Radar daily edition lands every morning with the incidents that need action. Free.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click