{"uuid": "22708ea3-f5d5-40a4-a5f7-a447b0a07643", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21635", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/2330", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21635\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nrds: sysctl: rds_tcp_{rcv,snd}buf: avoid using current->nsproxy\n\nAs mentioned in a previous commit of this series, using the 'net'\nstructure via 'current' is not recommended for different reasons:\n\n- Inconsistency: getting info from the reader's/writer's netns vs only\n  from the opener's netns.\n\n- current->nsproxy can be NULL in some cases, resulting in an 'Oops'\n  (null-ptr-deref), e.g. when the current task is exiting, as spotted by\n  syzbot [1] using acct(2).\n\nThe per-netns structure can be obtained from the table->data using\ncontainer_of(), then the 'net' one can be retrieved from the listen\nsocket (if available).\n\ud83d\udccf Published: 2025-01-19T10:17:53.832Z\n\ud83d\udccf Modified: 2025-01-19T10:17:53.832Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/de8d6de0ee27be4b2b1e5b06f04aeacbabbba492\n2. https://git.kernel.org/stable/c/7f5611cbc4871c7fb1ad36c2e5a9edad63dca95c", "creation_timestamp": "2025-01-19T10:58:39.000000Z"}