Skip to main content
VulnerabilityPublished Updated

CVE-2026-68300: Linux kernel · Improper Authentication

Affects Linux kernelSource CVE Database V5

0

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

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ bbd0d59809f923ea2b540cbd781b32110e249f6e, < ec2e157fc9678a9bc411305a25aec3fd337d7efb
Fixed in
  • ec2e157fc9678a9bc411305a25aec3fd337d7efb
LinuxLinuxAffected
  • ≥ bbd0d59809f923ea2b540cbd781b32110e249f6e, < a129792b3aef15002746c13522781d92ed3522c3
Fixed in
  • a129792b3aef15002746c13522781d92ed3522c3
LinuxLinuxAffected
  • ≥ bbd0d59809f923ea2b540cbd781b32110e249f6e, < 18957373920caf5cdaf5cf32e5d1d7a99ca7700a
Fixed in
  • 18957373920caf5cdaf5cf32e5d1d7a99ca7700a
LinuxLinuxAffected
  • ≥ bbd0d59809f923ea2b540cbd781b32110e249f6e, < 83f5031f2a6a49d696eb4cc0898345d12f9c6451
Fixed in
  • 83f5031f2a6a49d696eb4cc0898345d12f9c6451
LinuxLinuxAffected
  • ≥ bbd0d59809f923ea2b540cbd781b32110e249f6e, < 28c5fdce9dd955d2baf5e28987819b6d7cfaf646
Fixed in
  • 28c5fdce9dd955d2baf5e28987819b6d7cfaf646
LinuxLinuxAffected
  • ≥ bbd0d59809f923ea2b540cbd781b32110e249f6e, < 8e04823c120b376ef7dab14b60ebf6823aa16c14
Fixed in
  • 8e04823c120b376ef7dab14b60ebf6823aa16c14

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

Community reviews

Loading reviews…