{"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"}