14 matches found
Azure Linux 3.0 Security Update: kernel (CVE-2025-21636)
The version of kernel installed on the remote Azure Linux 3.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2025-21636 advisory. - In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: plpmtudprobeinterval: avoi...
CBL Mariner 2.0 Security Update: kernel (CVE-2025-21636)
The version of kernel installed on the remote CBL Mariner 2.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2025-21636 advisory. - In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: plpmtudprobeinterval: avoi...
CVE-2025-21636 affecting package kernel for versions less than 5.15.180.1-1
CVE-2025-21636 affecting package kernel for versions less than 5.15.180.1-1. An upgraded version of the package is available that resolves this issue...
CVE-2025-21636 affecting package kernel for versions less than 6.6.78.1-3
CVE-2025-21636 affecting package kernel for versions less than 6.6.78.1-3. An upgraded version of the package is available that resolves this issue...
Linux Distros Unpatched Vulnerability : CVE-2025-21636
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: plpmtudprobeinterval: avoid using current-nsproxy As mentioned in a previous...
BELL-CVE-2025-21636
Bulletin has no description...
CVE-2025-21636
In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: plpmtudprobeinterval: avoid using current-nsproxy As mentioned in a previous commit of this series, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsistency: getting info fro...
CVE-2025-21636
In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: plpmtudprobeinterval: avoid using current-nsproxy As mentioned in a previous commit of this series, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsistency: getting info fro...
CVE-2025-21636
In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: plpmtudprobeinterval: avoid using current-nsproxy As mentioned in a previous commit of this series, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsistency: getting info fro...
CVE-2025-21636
creationtimestamp| type| source ---|---|--- 2025-01-19 10:42:05+00:00| seen| https://infosec.exchange/users/cve/statuses/113854599992003984 2025-01-19 10:58:35+00:00| published-proof-of-concept| https://t.me/DarkWebInformerCVEAlerts/2329 2025-01-19 11:15:34+00:00| seen|...
CVE-2025-21636
In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: plpmtudprobeinterval: avoid using current-nsproxy As mentioned in a previous commit of this series, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsistency: getting info fro...
CVE-2025-21636
CVE-2025-21636 is a Linux kernel vulnerability where the code path for sctp: sysctl: plpmtud_probe_interval used current->nsproxy, risking NULL dereference when the task exits. The fix replaces use of current->nsproxy with obtaining the necessary net pointer from table->data via containe...
CVE-2025-21636 sctp: sysctl: plpmtud_probe_interval: avoid using current->nsproxy
In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: plpmtudprobeinterval: avoid using current-nsproxy As mentioned in a previous commit of this series, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsistency: getting info fro...
CVE-2025-21636 sctp: sysctl: plpmtud_probe_interval: avoid using current->nsproxy
In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: plpmtudprobeinterval: avoid using current-nsproxy As mentioned in a previous commit of this series, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsistency: getting info fro...