{"uuid": "98d94b51-24d2-499a-a32e-7f24dee915f0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21638", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/2327", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21638\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nsctp: sysctl: auth_enable: 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 'net' structure can be obtained from the table->data using\ncontainer_of().\n\nNote that table->data could also be used directly, but that would\nincrease the size of this fix, while 'sctp.ctl_sock' still needs to be\nretrieved from 'net' structure.\n\ud83d\udccf Published: 2025-01-19T10:17:56.084Z\n\ud83d\udccf Modified: 2025-01-19T10:17:56.084Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/1b67030d39f2b00f94ac1f0af11ba6657589e4d3\n2. https://git.kernel.org/stable/c/7ec30c54f339c640aa7e49d7e9f7bbed6bd42bf6\n3. https://git.kernel.org/stable/c/c184bc621e3cef03ac9ba81a50dda2dae6a21d36\n4. https://git.kernel.org/stable/c/15649fd5415eda664ef35780c2013adeb5d9c695", "creation_timestamp": "2025-01-19T10:58:33.000000Z"}