{"uuid": "4bf3446c-3b3f-4155-b877-f7e431826808", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21637", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/2328", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21637\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nsctp: sysctl: udp_port: 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:55.321Z\n\ud83d\udccf Modified: 2025-01-19T10:17:55.321Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/e919197fb8616331f5dc81e4c3cc3d12769cb725\n2. https://git.kernel.org/stable/c/55627918febdf9d71107a1e68d1528dc591c9a15\n3. https://git.kernel.org/stable/c/5b77d73f3be5102720fb685b9e6900e3500e1096\n4. https://git.kernel.org/stable/c/c10377bbc1972d858eaf0ab366a311b39f8ef1b6", "creation_timestamp": "2025-01-19T10:58:34.000000Z"}