CVE-2025-21639

The CVE-2025-21639 issue is in the Linux kernel SCTP sysctl handling (rto_min/rto_max) where current->nsproxy was used to read netns, risking a NULL pointer dereference and Oops when the task is exiting. The fix, as described in the initial document, replaces current->nsproxy usage with ret...

CVE-2025-21638 sctp: sysctl: auth_enable: avoid using current->nsproxy

In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: authenable: 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 from the...

CVE-2025-21639 sctp: sysctl: rto_min/max: avoid using current->nsproxy

In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: rtomin/max: 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 from the...

CVE-2025-21637 sctp: sysctl: udp_port: avoid using current->nsproxy

In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: udpport: 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 from the...

CVE-2025-21637

CVE-2025-21637 affects the Linux kernel SCTP sysctl path for udp_port. The issue arises from using current->nsproxy via the net structure, risking NULL nsproxy (e.g., when the current task is exiting) and potentially triggering a fault. The fix described in the sources relies on obtaining net ...

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

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-21635 rds: sysctl: rds_tcp_{rcv,snd}buf: avoid using current->nsproxy

In the Linux kernel, the following vulnerability has been resolved: rds: sysctl: rdstcprcv,sndbuf: 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 from the...

CVE-2025-21635

CVE-2025-21635 — Linux kernel (RDS): The vulnerability arises from using current->nsproxy in rds_tcp_rcvbuf/rds_tcp_sndbuf sysctl handling, which can cause a NULL pointer dereference when the current task is exiting and the netns proxy is NULL. The fix switches to obtaining the per-netns conte...

CVE-2025-21641: NULL Pointer Dereference

In the Linux kernel, the following vulnerability has been resolved: mptcp: sysctl: blackhole timeout: avoid using current-nsproxy As mentioned in the previous commit, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsistency: getting info from the...

CVE-2025-21642: NULL Pointer Dereference

In the Linux kernel, the following vulnerability has been resolved: mptcp: sysctl: sched: avoid using current-nsproxy Using the 'net' structure via 'current' is not recommended for different reasons. First, if the goal is to use it to read or write per-netns data, this is inconsistent with how th...

CVE-2025-21635: NULL Pointer Dereference

In the Linux kernel, the following vulnerability has been resolved: rds: sysctl: rdstcprcv,sndbuf: 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 from the...

CVE-2025-21636: NULL Pointer Dereference

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...

PT-2025-4319

Name of the Vulnerable Software and Affected Versions Linux kernel versions prior to 6.6.74 Description The issue concerns the Linux kernel, where using the 'net' structure via 'current' is not recommended due to inconsistency and potential null pointer dereferences. The 'net' structure can be...

PT-2025-4317

Name of the Vulnerable Software and Affected Versions Linux kernel versions prior to 6.6.74 Description The issue concerns the use of the current-nsproxy in the Linux kernel, specifically in the sctp module. This usage is not recommended due to inconsistency and potential null pointer dereference...

PT-2025-4318

Name of the Vulnerable Software and Affected Versions Linux kernel versions prior to 6.6.74 Description The issue concerns the use of current-nsproxy in the Linux kernel, which is not recommended due to inconsistency and potential null pointer dereferences. The net structure can be obtained from...

CVE-2022-4696: Release of Invalid Pointer or Reference

There exists a use-after-free vulnerability in the Linux kernel through iouring and the IORINGOPSPLICE operation. If IORINGOPSPLICE is missing the IOWQWORKFILES flag, which signals that the operation won't use current-nsproxy, so its reference counter is not increased. This assumption is not alwa...