CVE-2026-46168
In the Linux kernel, the following vulnerability has been resolved: mptcp: fix scheduling with atomic in timestamp sockopt Using lock_sock_fast() (atomic context) around sock_set_timestamp() and sock_set_timestamping() is unsafe, as both helpers can sleep. Replace lock_sock_fast() with sleepable lock_sock()/release_sock() to avoid scheduling while atomic panic.
Affected versions
Linux kernel versions
5.14
and later are affected. Fixed in
5.15.209,
6.1.175,
6.6.140,
6.12.88,
6.18.30,
7.0.7,
7.1-rc2
and their respective stable series.
References
The following references provide additional information about CVE-2026-46168 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.
-
PatchKernel patch commithttps://git.kernel.org/stable/c/0949d8bbbedbafe0136a1723c41eb823c2f1e09d
-
PatchKernel patch commithttps://git.kernel.org/stable/c/7eb513b42721bee4b96da69f6188d5a7783f210d
-
PatchKernel patch commithttps://git.kernel.org/stable/c/8a005fe451c73fd2b3d1faa5643c11e6bd07acfc
Frequently asked questions
-
What is CVE-2026-46168?
CVE-2026-46168 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 5.14 onward and has been patched in 5.15.209, 6.1.175, 6.6.140 and others. CVE-2026-46168 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-46168?
Yes — CVE-2026-46168 has been patched. Fixed versions include 5.15.209, 6.1.175, 6.6.140 and others. If you are running Linux kernel 5.14 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-46168 actively exploited?
No — CVE-2026-46168 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.