sctp: sysctl: cookie_hmac_alg: avoid using current->nsproxy
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3c68198e75111a905ac2412be12bf7b29099729b · < f0bb3935470684306e4e04793a20ac4c4b08de0b| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
sctp: sysctl: cookie_hmac_alg: 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.sctp_hmac_alg' is used.
From the CVE record · Linux
The Linux kernel’s SCTP cookie_hmac_alg sysctl can dereference a null pointer when the current task is exiting and its nsproxy is NULL, causing a kernel Oops. The issue was observed with a local acct(2) call; authentication requirements and user interaction are not specified.
Engineers running Linux kernels with the affected SCTP sysctl code should check their versions against the vendor advisory; affected versions are not listed in the input.