{"uuid": "9d29aa64-4d1a-4255-97e1-3935d95ce471", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21639", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/2326", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21639\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nsctp: sysctl: rto_min/max: 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, as this is the only\nmember needed from the 'net' structure, but that would increase the size\nof this fix, to use '*data' everywhere 'net->sctp.rto_min/max' is used.\n\ud83d\udccf Published: 2025-01-19T10:17:56.828Z\n\ud83d\udccf Modified: 2025-01-19T10:17:56.828Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/4059507e34aa5fe0fa9fd5b2b5f0c8b26ab2d482\n2. https://git.kernel.org/stable/c/dc9d0e3cfd16f66fbf0862857c6b391c8613ca9f\n3. https://git.kernel.org/stable/c/c87f1f6ade56c711f8736901e330685b453e420e\n4. https://git.kernel.org/stable/c/9fc17b76fc70763780aa78b38fcf4742384044a5", "creation_timestamp": "2025-01-19T10:58:33.000000Z"}