Skip to main content
VulnerabilityPublished Updated

CVE-2026-46168: Linux kernel · mptcp: fix scheduling with atomic in timestamp sockopt

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in ebeb70e29e37cfce899309cc2665a3bfe960ed94 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:34 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in ebeb70e29e37cfce899309cc2665a3bfe960ed94, e792cfb6aeaf65612cdf8e3ac431d65e66283654, b157dab93a7af44a84e78cf0cb311dde475cff5b +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 9061f24bf82ec2e92dd1e7c10b98b680db023d31, < ebeb70e29e37cfce899309cc2665a3bfe960ed94
Fixed in
  • ebeb70e29e37cfce899309cc2665a3bfe960ed94
LinuxLinuxAffected
  • ≥ 9061f24bf82ec2e92dd1e7c10b98b680db023d31, < e792cfb6aeaf65612cdf8e3ac431d65e66283654
Fixed in
  • e792cfb6aeaf65612cdf8e3ac431d65e66283654
LinuxLinuxAffected
  • ≥ 9061f24bf82ec2e92dd1e7c10b98b680db023d31, < b157dab93a7af44a84e78cf0cb311dde475cff5b
Fixed in
  • b157dab93a7af44a84e78cf0cb311dde475cff5b
LinuxLinuxAffected
  • ≥ 9061f24bf82ec2e92dd1e7c10b98b680db023d31, < b5c52908d52c6c8eb8933264aa6087a0600fd892
Fixed in
  • b5c52908d52c6c8eb8933264aa6087a0600fd892
LinuxLinuxAffected
  • ≥ 9061f24bf82ec2e92dd1e7c10b98b680db023d31, < 0949d8bbbedbafe0136a1723c41eb823c2f1e09d
Fixed in
  • 0949d8bbbedbafe0136a1723c41eb823c2f1e09d
LinuxLinuxAffected
  • ≥ 9061f24bf82ec2e92dd1e7c10b98b680db023d31, < 8a005fe451c73fd2b3d1faa5643c11e6bd07acfc
Fixed in
  • 8a005fe451c73fd2b3d1faa5643c11e6bd07acfc

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.

References

Community reviews

Loading reviews…