Answer in brief
CVE-2025-21635 records a Medium severity (CVSS 5.5) vulnerability in rds: sysctl: rds_tcp_{rcv,snd}buf: avoid using current->nsproxy. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c6a58ffed53612be86b758df1cdb0b0f4305e9cb <33b3e09a489a31b30342b77cc55290f025d95c7e || >=c6a58ffed53612be86b758df1cdb0b0f4305e9cb <de8d6de0ee27be4b2b1e5b06f04aeacbabbba492 || >=c6a58ffed53612be86b758df1cdb0b0f4305e9cb <7f5611cbc4871c7fb1ad36c2e5a9edad63dca95c | 33b3e09a489a31b30342b77cc55290f025d95c7e, de8d6de0ee27be4b2b1e5b06f04aeacbabbba492, 7f5611cbc4871c7fb1ad36c2e5a9edad63dca95c |
| Linux/Linuxgeneric | 4.6 | Not reported |
Published upstream
Jan 19, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 21, 2026
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).
Quoted source text, attributed separately from HOL analysis.