sctp: sysctl: rto_min/max: avoid using current->nsproxy
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4f3fdf3bc59cafd14c3bc2c2369efad34c7aa8b5 · < c87f1f6ade56c711f8736901e330685b453e420e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
sctp: sysctl: rto_min/max: 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, as this is the only member needed from the 'net' structure, but that would increase the size of this fix, to use '*data' everywhere 'net->sctp.rto_min/max' is used.
From the CVE record · Linux
The Linux kernel’s SCTP rto_min/max sysctl handling can dereference a null pointer when it obtains a network namespace through current->nsproxy. This can cause a kernel Oops when the current task is exiting; the report describes a case involving acct(2). The input does not establish a remote attack path or authentication requirement.
Engineers running Linux kernels with SCTP sysctl support should check their kernel vendor’s guidance; affected versions are not specified.