mptcp: fix scheduling with atomic in timestamp sockopt
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9061f24bf82ec2e92dd1e7c10b98b680db023d31 · < 7eb513b42721bee4b96da69f6188d5a7783f210d| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s MPTCP timestamp socket-option handling can call functions that sleep while holding a lock in atomic context. This can cause a kernel panic; the input does not specify an attack path, authentication requirements, or user interaction.
Operators running Linux kernels with MPTCP should check whether their kernel includes this fix; affected versions are not specified.