{"vulnerability": "CVE-2025-21635", "sightings": [{"uuid": "bac445c9-3513-4651-9431-68e5dbb3f7d9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21635", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"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"}, {"uuid": "5c0eb1ff-4a28-4e8c-90db-1908faa5a880", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21635", "type": "seen", "source": "https://t.me/cvedetector/15838", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21635 - \"Linux RDS rds_tcp buffer NULL Pointer Dereference\"\", \n  \"Content\": \"CVE ID : CVE-2025-21635 \nPublished : Jan. 19, 2025, 11:15 a.m. | 35\u00a0minutes ago \nDescription : 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). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"19 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-19T13:07:27.000000Z"}, {"uuid": "93295825-cf94-4f37-8cd7-9e261852e46f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21635", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113854599975962176", "content": "", "creation_timestamp": "2025-01-19T10:42:05.347467Z"}, {"uuid": "199b4150-2682-49df-8739-962623613476", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21635", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lg3p3knsey2j", "content": "", "creation_timestamp": "2025-01-19T11:15:32.161216Z"}, {"uuid": "641c86e9-e73e-49af-b8f1-001bd2784206", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21635", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lg3qyyefhp2e", "content": "", "creation_timestamp": "2025-01-19T11:49:54.385056Z"}, {"uuid": "570df754-8e9d-4dc0-a884-2322e864322a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21635", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}]}