CVE-2026-46168
Received Received - Intake
Linux Kernel MPTCP sockopt Timestamp Scheduling Fix

Publication date: 2026-05-28

Last updated on: 2026-05-28

Assigner: kernel.org

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-28
Last Modified
2026-05-28
Generated
2026-05-28
AI Q&A
2026-05-28
EPSS Evaluated
N/A
NVD
CVE-2026-46168
EUVD
EUVD-2026-32795
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
linux linux_kernel *
linux_kernel linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability in the Linux kernel involves improper locking in the Multipath TCP (mptcp) implementation. Specifically, the code used lock_sock_fast() in an atomic context around the functions sock_set_timestamp() and sock_set_timestamping(), but these functions can sleep, which is unsafe in atomic context.

The fix replaces lock_sock_fast() with the sleepable lock_sock() and release_sock() functions to avoid scheduling while in atomic context, preventing potential kernel panics.


How can this vulnerability impact me? :

This vulnerability can cause the Linux kernel to panic due to unsafe scheduling in atomic context. Kernel panics can lead to system crashes, resulting in downtime and potential loss of data or service availability.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart