CVE-2026-68300: Linux kernel · Improper Authentication
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical · fixed in ec2e157fc9678a9bc411305a25aec3fd337d7efb : patch Linux kernel as a priority.
Data as of 26 Oct 2026, 11:54 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers can reliably automate steps 1–4 of the kill chain
- Technical impact
- Total control over the software or total information disclosure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in ec2e157fc9678a9bc411305a25aec3fd337d7efb, a129792b3aef15002746c13522781d92ed3522c3, 18957373920caf5cdaf5cf32e5d1d7a99ca7700a +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Aug 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
|
Description
In the Linux kernel, the following vulnerability has been resolved: sctp: auth: verify auth requirement when auth_chunk is NULL sctp_auth_chunk_verify() returns true unconditionally when chunk->auth_chunk is NULL, silently skipping authentication. This is incorrect when: 1. skb_clone() failed in the BH receive path, leaving auth_chunk NULL. In sctp_endpoint_bh_rcv() asoc is NULL for new connections, so the early sctp_auth_recv_cid() check cannot catch this. 2. No AUTH chunk precedes COOKIE-ECHO, so skb_clone() is never called and auth_chunk remains NULL. Fix by checking sctp_auth_recv_cid() when auth_chunk is NULL: if authentication is required, return false to drop the chunk; otherwise continue normally.
References
- git.kernel.org/stable/c/a129792b3aef15002746c13522781d92ed3522c3 (opens in a new tab)
- git.kernel.org/stable/c/5a022ac51ad83b4ce6c898f4b9eefc65bd26b247 (opens in a new tab)
- git.kernel.org/stable/c/6caf0e8590c0bf05a76b0d387726adf3a6f3725c (opens in a new tab)
- git.kernel.org/stable/c/ec2e157fc9678a9bc411305a25aec3fd337d7efb (opens in a new tab)
- git.kernel.org/stable/c/28c5fdce9dd955d2baf5e28987819b6d7cfaf646 (opens in a new tab)
- git.kernel.org/stable/c/18957373920caf5cdaf5cf32e5d1d7a99ca7700a (opens in a new tab)
- git.kernel.org/stable/c/83f5031f2a6a49d696eb4cc0898345d12f9c6451 (opens in a new tab)
- git.kernel.org/stable/c/8e04823c120b376ef7dab14b60ebf6823aa16c14 (opens in a new tab)