CVE-2026-31430: Linux kernel · X.509: Fix out-of-bounds access when parsing extensions
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d702c3408213bb12bd570bb97204d8340d141c51 : update Linux kernel when convenient.
Data as of 5 Nov 2026, 22:04 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-05.
- Patch
- Available – fixed in d702c3408213bb12bd570bb97204d8340d141c51, 206121294b9cf27f0589857f80d64f87e496ffb2, 672b526def1f94c1be8eb11b885b803da0d8c2f1 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 5 Nov 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– |
Description
In the Linux kernel, the following vulnerability has been resolved: X.509: Fix out-of-bounds access when parsing extensions Leo reports an out-of-bounds access when parsing a certificate with empty Basic Constraints or Key Usage extension because the first byte of the extension is read before checking its length. Fix it. The bug can be triggered by an unprivileged user by submitting a specially crafted certificate to the kernel through the keyrings(7) API. Leo has demonstrated this with a proof-of-concept program responsibly disclosed off-list.
References
- git.kernel.org/stable/c/672b526def1f94c1be8eb11b885b803da0d8c2f1 (opens in a new tab)
- git.kernel.org/stable/c/30ab358fad0c7daa1d282ec48089901b21b36a20 (opens in a new tab)
- git.kernel.org/stable/c/206121294b9cf27f0589857f80d64f87e496ffb2 (opens in a new tab)
- git.kernel.org/stable/c/7fb4dadc2734f4020d7543d688b8d49c8e569c61 (opens in a new tab)
- git.kernel.org/stable/c/d702c3408213bb12bd570bb97204d8340d141c51 (opens in a new tab)