{"vulnerability": "CVE-2025-21641", "sightings": [{"uuid": "f0759d9e-7466-4621-8f50-7e6140b4bb0d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21641", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/2324", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21641\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: sysctl: blackhole timeout: avoid using current-&gt;nsproxy\n\nAs mentioned in the previous commit, using the 'net' structure via\n'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-&gt;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 'pernet' structure can be obtained from the table-&gt;data using\ncontainer_of().\n\ud83d\udccf Published: 2025-01-19T10:17:58.351Z\n\ud83d\udccf Modified: 2025-01-19T10:17:58.351Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/4c74fbdc5ab95b13945be01e6065940b68222db7\n2. https://git.kernel.org/stable/c/92cf7a51bdae24a32c592adcdd59a773ae149289", "creation_timestamp": "2025-01-19T10:58:28.000000Z"}, {"uuid": "27c454ed-9f96-4df5-a56c-d1e75b6c664e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21641", "type": "seen", "source": "https://t.me/cvedetector/15833", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21641 - Linux Kernel MPTCP Sysctl Blackhole Timeout Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21641 \nPublished : Jan. 19, 2025, 11:15 a.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nmptcp: sysctl: blackhole timeout: avoid using current-&gt;nsproxy  \n  \nAs mentioned in the previous commit, using the 'net' structure via  \n'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-&gt;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 'pernet' structure can be obtained from the table-&gt;data using  \ncontainer_of(). \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:20.000000Z"}, {"uuid": "428b6bae-9a56-4caf-9111-3a758b313b27", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21641", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113854659075710792", "content": "", "creation_timestamp": "2025-01-19T10:57:07.303734Z"}, {"uuid": "8fe9d407-bac0-4f87-91b7-d7b3faf8df18", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21641", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lg3p3zmg6q2p", "content": "", "creation_timestamp": "2025-01-19T11:15:47.674668Z"}, {"uuid": "9a46720e-cc9b-476d-bf4b-2cc44e1de568", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21641", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lg3qyyqg6j2q", "content": "", "creation_timestamp": "2025-01-19T11:49:56.073528Z"}]}