sctp: sysctl: udp_port: avoid using current->nsproxy
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
sctp: sysctl: udp_port: avoid using current->nsproxy
As mentioned in a previous commit of this series, using the 'net' structure via 'current' is not recommended for different reasons:
- Inconsistency: getting info from the reader's/writer's netns vs only from the opener's netns.
- current->nsproxy can be NULL in some cases, resulting in an 'Oops' (null-ptr-deref), e.g. when the current task is exiting, as spotted by syzbot [1] using acct(2).
The 'net' structure can be obtained from the table->data using container_of().
Note that table->data could also be used directly, but that would increase the size of this fix, while 'sctp.ctl_sock' still needs to be retrieved from 'net' structure.
From the CVE record · Linux
The Linux kernel’s SCTP udp_port sysctl can dereference a NULL pointer when the current task is exiting and current->nsproxy is NULL. This can cause a kernel Oops; the input does not establish an attacker path or authentication or user-interaction requirements.
Teams running Linux kernels with the affected SCTP sysctl code should check their versions; no affected version range is provided.