CVE-2026-68300
Linux kernel vulnerability
- Published10 Aug 2026
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://git.kernel.org/stable/c/18957373920caf5cdaf5cf32e5d1d7a99ca7700a
- https://git.kernel.org/stable/c/28c5fdce9dd955d2baf5e28987819b6d7cfaf646
- https://git.kernel.org/stable/c/5a022ac51ad83b4ce6c898f4b9eefc65bd26b247
- https://git.kernel.org/stable/c/6caf0e8590c0bf05a76b0d387726adf3a6f3725c
- https://git.kernel.org/stable/c/83f5031f2a6a49d696eb4cc0898345d12f9c6451
- https://git.kernel.org/stable/c/8e04823c120b376ef7dab14b60ebf6823aa16c14
- https://git.kernel.org/stable/c/a129792b3aef15002746c13522781d92ed3522c3
- https://git.kernel.org/stable/c/ec2e157fc9678a9bc411305a25aec3fd337d7efb
Frequently asked
Is CVE-2026-68300 being actively exploited?
CVE-2026-68300 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.59%.
How severe is CVE-2026-68300?
CVE-2026-68300 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.59% probability of exploitation.
How do I fix CVE-2026-68300?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-68300 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.