In the Linux kernel, the following vulnerability has been resolved:
rds: sysctl: rds_tcp_{rcv,snd}buf: 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 per-netns structure can be obtained from the table->data using
container_of(), then the 'net' one can be retrieved from the listen
socket (if available).
Metrics
Affected Vendors & Products
References
History
Thu, 13 Feb 2025 01:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | CWE-476 |
Mon, 20 Jan 2025 14:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
cvssV3_1
|
Sun, 19 Jan 2025 10:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | In the Linux kernel, the following vulnerability has been resolved: rds: sysctl: rds_tcp_{rcv,snd}buf: 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 per-netns structure can be obtained from the table->data using container_of(), then the 'net' one can be retrieved from the listen socket (if available). | |
Title | rds: sysctl: rds_tcp_{rcv,snd}buf: avoid using current->nsproxy | |
References |
|

Status: PUBLISHED
Assigner: Linux
Published: 2025-01-19T10:17:53.832Z
Updated: 2025-01-20T06:29:51.847Z
Reserved: 2024-12-29T08:45:45.726Z
Link: CVE-2025-21635

No data.

Status : Received
Published: 2025-01-19T11:15:09.000
Modified: 2025-01-19T11:15:09.000
Link: CVE-2025-21635
