CVE-2026-46168: mptcp: fix scheduling with atomic in timestamp sockopt
In the Linux kernel, the following vulnerability has been resolved:
mptcp: fix scheduling with atomic in timestamp sockopt
Using locksockfast() (atomic context) around socksettimestamp() and socksettimestamping() is unsafe, as both helpers can sleep.
Replace locksockfast() with sleepable locksock()/releasesock() to avoid scheduling while atomic panic.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.141.1-1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-46168?
The severity of CVE-2026-46168 is classified as risk level 21.
How do I fix CVE-2026-46168?
To fix CVE-2026-46168, ensure that the implementation uses sleepable locks instead of atomic locks in the affected functions.
What systems are affected by CVE-2026-46168?
CVE-2026-46168 affects the Linux Kernel specifically in its mptcp (MultiPath TCP) implementation.
Who resolved CVE-2026-46168?
CVE-2026-46168 was resolved by the Linux Kernel developers in a recent update.
What are the potential risks of CVE-2026-46168?
The potential risks of CVE-2026-46168 include improper scheduling leading to system instability or unexpected behavior in the MultiPath TCP functionality.