{"vulnerability": "CVE-2025-2163", "sightings": [{"uuid": "c23271a8-ce44-4cc3-abb7-9485a9d19a9c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21634", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "570df754-8e9d-4dc0-a884-2322e864322a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21635", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "bac445c9-3513-4651-9431-68e5dbb3f7d9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21635", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "21b6b96a-9219-4050-b11a-470110a761e3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21636", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/2329", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21636\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nsctp: sysctl: plpmtud_probe_interval: 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.probe_interval' is\nused.\n\ud83d\udccf Published: 2025-01-19T10:17:54.576Z\n\ud83d\udccf Modified: 2025-01-19T10:17:54.576Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/44ee8635922b6eb940faddb961a8347c6857d722\n2. https://git.kernel.org/stable/c/284a221f8fa503628432c7bb5108277c688c6ffa\n3. https://git.kernel.org/stable/c/bcf8c60074e81ed2ac2d35130917175a3949c917\n4. https://git.kernel.org/stable/c/6259d2484d0ceff42245d1f09cc8cb6ee72d847a", "creation_timestamp": "2025-01-19T10:58:35.000000Z"}, {"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"}, {"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"}, {"uuid": "0fa91146-da84-46ac-acc5-04187dfb5ffb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21634", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/2331", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21634\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ncgroup/cpuset: remove kernfs active break\n\nA warning was found:\n\nWARNING: CPU: 10 PID: 3486953 at fs/kernfs/file.c:828\nCPU: 10 PID: 3486953 Comm: rmdir Kdump: loaded Tainted: G\nRIP: 0010:kernfs_should_drain_open_files+0x1a1/0x1b0\nRSP: 0018:ffff8881107ef9e0 EFLAGS: 00010202\nRAX: 0000000080000002 RBX: ffff888154738c00 RCX: dffffc0000000000\nRDX: 0000000000000007 RSI: 0000000000000004 RDI: ffff888154738c04\nRBP: ffff888154738c04 R08: ffffffffaf27fa15 R09: ffffed102a8e7180\nR10: ffff888154738c07 R11: 0000000000000000 R12: ffff888154738c08\nR13: ffff888750f8c000 R14: ffff888750f8c0e8 R15: ffff888154738ca0\nFS:  00007f84cd0be740(0000) GS:ffff8887ddc00000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000555f9fbe00c8 CR3: 0000000153eec001 CR4: 0000000000370ee0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n kernfs_drain+0x15e/0x2f0\n __kernfs_remove+0x165/0x300\n kernfs_remove_by_name_ns+0x7b/0xc0\n cgroup_rm_file+0x154/0x1c0\n cgroup_addrm_files+0x1c2/0x1f0\n css_clear_dir+0x77/0x110\n kill_css+0x4c/0x1b0\n cgroup_destroy_locked+0x194/0x380\n cgroup_rmdir+0x2a/0x140\n\nIt can be explained by:\nrmdir     echo 1 > cpuset.cpus\n    kernfs_fop_write_iter // active=0\ncgroup_rm_file\nkernfs_remove_by_name_ns kernfs_get_active // active=1\n__kernfs_remove       // active=0x80000002\nkernfs_drain   cpuset_write_resmask\nwait_event\n//waiting (active == 0x80000001)\n    kernfs_break_active_protection\n    // active = 0x80000001\n// continue\n    kernfs_unbreak_active_protection\n    // active = 0x80000002\n...\nkernfs_should_drain_open_files\n// warning occurs\n    kernfs_put_active\n\nThis warning is caused by 'kernfs_break_active_protection' when it is\nwriting to cpuset.cpus, and the cgroup is removed concurrently.\n\nThe commit 3a5a6d0c2b03 (\"cpuset: don't nest cgroup_mutex inside\nget_online_cpus()\") made cpuset_hotplug_workfn asynchronous, This change\ninvolves calling flush_work(), which can create a multiple processes\ncircular locking dependency that involve cgroup_mutex, potentially leading\nto a deadlock. To avoid deadlock. the commit 76bb5ab8f6e3 (\"cpuset: break\nkernfs active protection in cpuset_write_resmask()\") added\n'kernfs_break_active_protection' in the cpuset_write_resmask. This could\nlead to this warning.\n\nAfter the commit 2125c0034c5d (\"cgroup/cpuset: Make cpuset hotplug\nprocessing synchronous\"), the cpuset_write_resmask no longer needs to\nwait the hotplug to finish, which means that concurrent hotplug and cpuset\noperations are no longer possible. Therefore, the deadlock doesn't exist\nanymore and it does not have to 'break active protection' now. To fix this\nwarning, just remove kernfs_break_active_protection operation in the\n'cpuset_write_resmask'.\n\ud83d\udccf Published: 2025-01-19T10:17:52.983Z\n\ud83d\udccf Modified: 2025-01-19T10:17:52.983Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/11cb1d643a74665a4e14749414f48f82cbc15c64\n2. https://git.kernel.org/stable/c/3cb97a927fffe443e1e7e8eddbfebfdb062e86ed", "creation_timestamp": "2025-01-19T10:58:39.000000Z"}, {"uuid": "22708ea3-f5d5-40a4-a5f7-a447b0a07643", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21635", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/2330", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21635\n\ud83d\udd39 Description: 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).\n\ud83d\udccf Published: 2025-01-19T10:17:53.832Z\n\ud83d\udccf Modified: 2025-01-19T10:17:53.832Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/de8d6de0ee27be4b2b1e5b06f04aeacbabbba492\n2. https://git.kernel.org/stable/c/7f5611cbc4871c7fb1ad36c2e5a9edad63dca95c", "creation_timestamp": "2025-01-19T10:58:39.000000Z"}, {"uuid": "39328011-46cc-41ae-a121-83c85c1103fe", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-2163", "type": "seen", "source": "https://t.me/cvedetector/20352", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-2163 - Zoorum Comments for WordPress CSRF Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-2163 \nPublished : March 15, 2025, 4:15 a.m. | 1\u00a0hour, 35\u00a0minutes ago \nDescription : The Zoorum Comments plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 0.9. This is due to missing or incorrect nonce validation on  the zoorum_set_options() function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. \nSeverity: 6.1 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"15 Mar 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-03-15T06:55:38.000000Z"}, {"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"}, {"uuid": "8379f2aa-0bb5-47ae-98e9-65df907d088e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21638", "type": "seen", "source": "https://t.me/cvedetector/15831", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21638 - Linux SCTP sysctl auth enables NULL Pointer Dereference\", \n  \"Content\": \"CVE ID : CVE-2025-21638 \nPublished : Jan. 19, 2025, 11:15 a.m. | 35\u00a0minutes ago \nDescription : 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. \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:15.000000Z"}, {"uuid": "7834740e-a610-4b05-936b-6b5d07fa7be6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21637", "type": "seen", "source": "https://t.me/cvedetector/15830", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21637 - Linux Kernel SCTP sysctl null pointer dereference vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21637 \nPublished : Jan. 19, 2025, 11:15 a.m. | 35\u00a0minutes ago \nDescription : 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. \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:15.000000Z"}, {"uuid": "adc424dc-0a6a-4816-8ec7-0859ca215f0e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21636", "type": "seen", "source": "https://t.me/cvedetector/15829", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21636 - Linux Kernel SCTP sysctl NULL Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21636 \nPublished : Jan. 19, 2025, 11:15 a.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nsctp: sysctl: plpmtud_probe_interval: 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.probe_interval' is  \nused. \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:14.000000Z"}, {"uuid": "4af11cb7-1f9e-4937-b937-cf86b94691b3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21634", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "4733d4d2-c646-4d91-aa28-b04297a229c4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21630", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfrtzwcqke2h", "content": "", "creation_timestamp": "2025-01-15T13:17:28.284608Z"}, {"uuid": "c95c3574-3674-464e-9c2d-4cdd0a15b940", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21631", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113854523662801149", "content": "", "creation_timestamp": "2025-01-19T10:22:41.116780Z"}, {"uuid": "45cb10b5-c7af-4ce7-86b1-24cd48ece877", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21633", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113854523695820482", "content": "", "creation_timestamp": "2025-01-19T10:22:41.498619Z"}, {"uuid": "316a04c2-c387-448f-bd0a-6d8ca6f67dc0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21632", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113854523680706571", "content": "", "creation_timestamp": "2025-01-19T10:22:41.746203Z"}, {"uuid": "3867e5bb-63db-4298-8917-876320e05950", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21634", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113854523711368285", "content": "", "creation_timestamp": "2025-01-19T10:22:41.818519Z"}, {"uuid": "1f90f5d5-96c2-4025-a5b5-d54c3f0734c2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21631", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113854540866743586", "content": "", "creation_timestamp": "2025-01-19T10:27:03.449737Z"}, {"uuid": "125c84dc-3df5-40e5-966c-30b590b087ab", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21632", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113854540885430559", "content": "", "creation_timestamp": "2025-01-19T10:27:03.603942Z"}, {"uuid": "28d499a6-c1c2-4ac5-893e-8cfe54b5b115", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21633", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113854540900686012", "content": "", "creation_timestamp": "2025-01-19T10:27:03.962742Z"}, {"uuid": "82149d0c-33c7-4a04-ae7b-e0560e144062", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21634", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113854540915826060", "content": "", "creation_timestamp": "2025-01-19T10:27:04.209309Z"}, {"uuid": "93295825-cf94-4f37-8cd7-9e261852e46f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21635", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113854599975962176", "content": "", "creation_timestamp": "2025-01-19T10:42:05.347467Z"}, {"uuid": "5bc215a1-e09c-43b9-aaf7-999ecc711609", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21636", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113854599992003984", "content": "", "creation_timestamp": "2025-01-19T10:42:05.819191Z"}, {"uuid": "776ff503-8765-4aa3-bbe0-dbe938a201e6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21637", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113854600026889663", "content": "", "creation_timestamp": "2025-01-19T10:42:06.110703Z"}, {"uuid": "6f24eb91-f153-47c0-96b2-bcb21ed5ce66", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21638", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113854600041661024", "content": "", "creation_timestamp": "2025-01-19T10:42:06.370674Z"}, {"uuid": "05d3038c-e122-4367-8723-c57d9452377c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21639", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113854659043882523", "content": "", "creation_timestamp": "2025-01-19T10:57:07.007996Z"}, {"uuid": "390e4537-fc72-41be-932a-05fdeb1df46c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21631", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lg3p3bkyp22f", "content": "", "creation_timestamp": "2025-01-19T11:15:22.412909Z"}, {"uuid": "f6264f0c-c3d7-4150-a617-b6734c9bdf2b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21632", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lg3p3drcpq2j", "content": "", "creation_timestamp": "2025-01-19T11:15:24.786623Z"}, {"uuid": "ff031e60-abd3-41fe-94b5-480f1f6064c5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21633", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lg3p3fthy22t", "content": "", "creation_timestamp": "2025-01-19T11:15:26.883417Z"}, {"uuid": "4157c028-3936-4cc4-a8b7-5803d787d365", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21634", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lg3p3hwndm2w", "content": "", "creation_timestamp": "2025-01-19T11:15:29.012477Z"}, {"uuid": "199b4150-2682-49df-8739-962623613476", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21635", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lg3p3knsey2j", "content": "", "creation_timestamp": "2025-01-19T11:15:32.161216Z"}, {"uuid": "c723e37f-f644-4a8b-93f0-797dee8092d5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21636", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lg3p3n6ii62c", "content": "", "creation_timestamp": "2025-01-19T11:15:34.596324Z"}, {"uuid": "23292435-1025-49db-91af-7c1c1a87098c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21637", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lg3p3pi4oy2s", "content": "", "creation_timestamp": "2025-01-19T11:15:37.106086Z"}, {"uuid": "a154745c-0e58-4e9c-a5d2-5d91072a18bc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21638", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lg3p3rogtk2f", "content": "", "creation_timestamp": "2025-01-19T11:15:39.146943Z"}, {"uuid": "df9ac851-8ce3-4257-8135-01f87c7099b9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21639", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lg3p3ueqfd2j", "content": "", "creation_timestamp": "2025-01-19T11:15:42.013645Z"}, {"uuid": "c0114d9c-e84d-4a8b-b265-630097a10528", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21637", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lg3qyy7egl2r", "content": "", "creation_timestamp": "2025-01-19T11:49:53.844718Z"}, {"uuid": "641c86e9-e73e-49af-b8f1-001bd2784206", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21635", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lg3qyyefhp2e", "content": "", "creation_timestamp": "2025-01-19T11:49:54.385056Z"}, {"uuid": "83ba1a12-b3bb-4f41-9ac3-564eefeea6f6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21636", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lg3qyyltng2b", "content": "", "creation_timestamp": "2025-01-19T11:49:55.489347Z"}, {"uuid": "cc407b34-2fb1-4176-971a-d419402be60b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21638", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lg3qyz2ncg2h", "content": "", "creation_timestamp": "2025-01-19T11:49:56.741836Z"}, {"uuid": "d0e72f65-4d89-4d88-9df1-f509bbbe22e7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21632", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/113854981239513388", "content": "", "creation_timestamp": "2025-01-19T12:19:02.915901Z"}, {"uuid": "82a4e15e-22d2-4e82-ba8a-1ff20ce8b456", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-2163", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lkfdkxuadl26", "content": "", "creation_timestamp": "2025-03-15T04:56:50.643020Z"}, {"uuid": "fb559017-0d40-4965-9f78-6877b6a1f470", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21630", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/1750", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21630\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/net: always initialize kmsg->msg.msg_inq upfront\n\nsyzbot reports that ->msg_inq may get used uinitialized from the\nfollowing path:\n\nBUG: KMSAN: uninit-value in io_recv_buf_select io_uring/net.c:1094 [inline]\nBUG: KMSAN: uninit-value in io_recv+0x930/0x1f90 io_uring/net.c:1158\n io_recv_buf_select io_uring/net.c:1094 [inline]\n io_recv+0x930/0x1f90 io_uring/net.c:1158\n io_issue_sqe+0x420/0x2130 io_uring/io_uring.c:1740\n io_queue_sqe io_uring/io_uring.c:1950 [inline]\n io_req_task_submit+0xfa/0x1d0 io_uring/io_uring.c:1374\n io_handle_tw_list+0x55f/0x5c0 io_uring/io_uring.c:1057\n tctx_task_work_run+0x109/0x3e0 io_uring/io_uring.c:1121\n tctx_task_work+0x6d/0xc0 io_uring/io_uring.c:1139\n task_work_run+0x268/0x310 kernel/task_work.c:239\n io_run_task_work+0x43a/0x4a0 io_uring/io_uring.h:343\n io_cqring_wait io_uring/io_uring.c:2527 [inline]\n __do_sys_io_uring_enter io_uring/io_uring.c:3439 [inline]\n __se_sys_io_uring_enter+0x204f/0x4ce0 io_uring/io_uring.c:3330\n __x64_sys_io_uring_enter+0x11f/0x1a0 io_uring/io_uring.c:3330\n x64_sys_call+0xce5/0x3c30 arch/x86/include/generated/asm/syscalls_64.h:427\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nand it is correct, as it's never initialized upfront. Hence the first\nsubmission can end up using it uninitialized, if the recv wasn't\nsuccessful and the networking stack didn't honor ->msg_get_inq being set\nand filling in the output value of ->msg_inq as requested.\n\nSet it to 0 upfront when it's allocated, just to silence this KMSAN\nwarning. There's no side effect of using it uninitialized, it'll just\npotentially cause the next receive to use a recv value hint that's not\naccurate.\n\ud83d\udccf Published: 2025-01-15T13:06:01.027Z\n\ud83d\udccf Modified: 2025-01-15T13:06:01.027Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/127c280067167beb88461cd930f7c7a4bb3c7239\n2. https://git.kernel.org/stable/c/c6e60a0a68b7e6b3c7e33863a16e8e88ba9eee6f", "creation_timestamp": "2025-01-15T14:18:43.000000Z"}, {"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"}, {"uuid": "0a014a1a-bf01-4a97-ad99-98956a54ec80", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-2163", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/7659", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-2163\n\ud83d\udd25 CVSS Score: 6.1 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N)\n\ud83d\udd39 Description: The Zoorum Comments plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 0.9. This is due to missing or incorrect nonce validation on  the zoorum_set_options() function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.\n\ud83d\udccf Published: 2025-03-15T03:23:23.156Z\n\ud83d\udccf Modified: 2025-03-15T03:23:23.156Z\n\ud83d\udd17 References:\n1. https://www.wordfence.com/threat-intel/vulnerabilities/id/2b58fb0f-c7ac-4ee6-84f1-ac14617a7c2b?source=cve\n2. https://plugins.trac.wordpress.org/browser/zoorum-comments/tags/0.9/zoorum-comments-admin.php#L18\n3. https://plugins.trac.wordpress.org/browser/zoorum-comments/tags/0.9/zoorum-comments-admin.php#L38\n4. https://wordpress.org/plugins/zoorum-comments/", "creation_timestamp": "2025-03-15T03:49:06.000000Z"}, {"uuid": "0d9594ef-b06e-4350-a00a-9edd5c59d75b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21630", "type": "seen", "source": "https://t.me/cvedetector/15442", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21630 - Linux Kernel: io_uring: Uninitialized Message Queue Inquire\", \n  \"Content\": \"CVE ID : CVE-2025-21630 \nPublished : Jan. 15, 2025, 1:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nio_uring/net: always initialize kmsg->msg.msg_inq upfront  \n  \nsyzbot reports that ->msg_inq may get used uinitialized from the  \nfollowing path:  \n  \nBUG: KMSAN: uninit-value in io_recv_buf_select io_uring/net.c:1094 [inline]  \nBUG: KMSAN: uninit-value in io_recv+0x930/0x1f90 io_uring/net.c:1158  \n io_recv_buf_select io_uring/net.c:1094 [inline]  \n io_recv+0x930/0x1f90 io_uring/net.c:1158  \n io_issue_sqe+0x420/0x2130 io_uring/io_uring.c:1740  \n io_queue_sqe io_uring/io_uring.c:1950 [inline]  \n io_req_task_submit+0xfa/0x1d0 io_uring/io_uring.c:1374  \n io_handle_tw_list+0x55f/0x5c0 io_uring/io_uring.c:1057  \n tctx_task_work_run+0x109/0x3e0 io_uring/io_uring.c:1121  \n tctx_task_work+0x6d/0xc0 io_uring/io_uring.c:1139  \n task_work_run+0x268/0x310 kernel/task_work.c:239  \n io_run_task_work+0x43a/0x4a0 io_uring/io_uring.h:343  \n io_cqring_wait io_uring/io_uring.c:2527 [inline]  \n __do_sys_io_uring_enter io_uring/io_uring.c:3439 [inline]  \n __se_sys_io_uring_enter+0x204f/0x4ce0 io_uring/io_uring.c:3330  \n __x64_sys_io_uring_enter+0x11f/0x1a0 io_uring/io_uring.c:3330  \n x64_sys_call+0xce5/0x3c30 arch/x86/include/generated/asm/syscalls_64.h:427  \n do_syscall_x64 arch/x86/entry/common.c:52 [inline]  \n do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  \n entry_SYSCALL_64_after_hwframe+0x77/0x7f  \n  \nand it is correct, as it's never initialized upfront. Hence the first  \nsubmission can end up using it uninitialized, if the recv wasn't  \nsuccessful and the networking stack didn't honor ->msg_get_inq being set  \nand filling in the output value of ->msg_inq as requested.  \n  \nSet it to 0 upfront when it's allocated, just to silence this KMSAN  \nwarning. There's no side effect of using it uninitialized, it'll just  \npotentially cause the next receive to use a recv value hint that's not  \naccurate. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"15 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-15T15:06:41.000000Z"}, {"uuid": "de5e0efc-9f0c-466f-b04d-f0139c2287dc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21639", "type": "seen", "source": "https://t.me/cvedetector/15839", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21639 - Linux Kernel SCTP - Use Of Null Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21639 \nPublished : Jan. 19, 2025, 11:15 a.m. | 35\u00a0minutes ago \nDescription : 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. \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:28.000000Z"}]}