CVE-2026-46168

Analyzed Analyzed - Analysis Complete

Linux Kernel MPTCP sockopt Timestamp Scheduling Fix

Publication date: 2026-05-28

Last updated on: 2026-06-10

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-06-10

Generated

2026-07-08

AI Q&A

2026-05-28

EPSS Evaluated

2026-07-06

NVD

CVE-2026-46168

EUVD

EUVD-2026-32795

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	7.1
linux	linux_kernel	From 6.13 (inc) to 6.18.30 (exc)
linux	linux_kernel	From 5.16 (inc) to 6.1.175 (exc)
linux	linux_kernel	From 6.19 (inc) to 7.0.7 (exc)
linux	linux_kernel	From 6.7 (inc) to 6.12.88 (exc)
linux	linux_kernel	From 6.2 (inc) to 6.6.140 (exc)
linux	linux_kernel	From 5.14 (inc) to 5.15.209 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

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.

Impact Analysis

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.

Hi! I’m here to help you understand CVE-2026-46168. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70