CVE-2026-93213: Linux kernel · of: fix out-of-bounds read in of_alias_scan() stem parser
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in fd0c7bbda81c0e0c1cb7b68d267b87371584f560 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:16 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in fd0c7bbda81c0e0c1cb7b68d267b87371584f560, f7f6c3e32a31f2e1ed12075e8cd22b370a84e67a, da7a80ddc610a19b0378016a4d816b9355f013a7 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 24 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel as indicated by multiple fixed commits. Users and administrators should update to a kernel version that includes these fixes to remediate the vulnerability.
Description
A vulnerability in the Linux kernel's device tree alias parser (of_alias_scan) caused an out-of-bounds read due to improper boundary checking. The parser checked a character before verifying bounds, leading to a read before the property name when the name was empty or consisted only of digits. This issue has been fixed by correcting the boundary check order.
References
- git.kernel.org/stable/c/fd0c7bbda81c0e0c1cb7b68d267b87371584f560 (opens in a new tab)
- git.kernel.org/stable/c/958d7ee9fcf008ef9d2072c6410ee1bf6abf3b64 (opens in a new tab)
- git.kernel.org/stable/c/f7f6c3e32a31f2e1ed12075e8cd22b370a84e67a (opens in a new tab)
- git.kernel.org/stable/c/da7a80ddc610a19b0378016a4d816b9355f013a7 (opens in a new tab)
- git.kernel.org/stable/c/96a9c984dd7c3589a2707a32b62802f98311dbfd (opens in a new tab)
- git.kernel.org/stable/c/9253cfc5a85be1494ce56b4fc6f2d2b509440910 (opens in a new tab)
- git.kernel.org/stable/c/acd1b49043366f43e932308b4db7d3ce568eeadb (opens in a new tab)
- git.kernel.org/stable/c/5bb01c657ff9fc807c2c592ca18af34c4fc3bc6f (opens in a new tab)