CVE-2026-63828: Linux kernel · apparmor: mediate the implicit connect of TCP fast open sendmsg
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 8.4 High.
Data as of 16 Nov 2026, 15:22 UTC
Thin evidence
One scorer or none| CNA (Linux) | CVSS 3.1 | 8.4 |
|---|
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Jul 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 15 Nov 2026.
What to do
AI-suggested
A fix for this vulnerability has been implemented in the Linux kernel by modifying AppArmor to mediate the implicit connect operation when MSG_FASTOPEN is used in sendmsg()/sendto() calls. Users and administrators should apply the official Linux kernel updates that include this patch to ensure proper enforcement of connect permissions. Since this is a kernel-level fix, upgrading to a patched kernel version is the recommended remediation. No alternative mitigations are indicated in the advisory.
Description
CVE-2026-63828 is a high-severity vulnerability in the Linux kernel related to AppArmor's mediation of TCP Fast Open connections. The flaw allows a confined task to bypass connect mediation by using sendmsg()/sendto() with MSG_FASTOPEN, which implicitly combines connect and write operations. This occurs because AppArmor only checked send permissions but not connect permissions for these operations, allowing unauthorized outbound TCP/MPTCP connections. The issue has been addressed by adding explicit mediation of the implicit connect when MSG_FASTOPEN is set, aligning AppArmor's behavior with other security modules like SELinux and Tomoyo.
References
- git.kernel.org/stable/c/a16714e7cf2baa98ba2efddd5d6cbac641f4e76b (opens in a new tab)
- git.kernel.org/stable/c/20383429b56974507c465d016e5238b189f7a246 (opens in a new tab)
- git.kernel.org/stable/c/7f57428ce00891d26b0f087ef754a4d820ec83aa (opens in a new tab)
- git.kernel.org/stable/c/faea60deaa05c76f0772650f42eafde12bd39d93 (opens in a new tab)
- git.kernel.org/stable/c/07b71c342382b854ab8030b244aeab6a7228ad7d (opens in a new tab)
- git.kernel.org/stable/c/4a69b83045d3195d5b9a9b053ad840ddb2998b4e (opens in a new tab)
- git.kernel.org/stable/c/45ebb934ea50b436ce49b2f159f090dab0d7fa28 (opens in a new tab)
- git.kernel.org/stable/c/4d587cd8a72155089a627130bbd4716ec0856e21 (opens in a new tab)