CVE-2025-21639Medium· 5.5▾ SunlitIn the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: rto_min/max: avoid using current->nsproxy As mentioned in a previous commit of this series, using the 'net' structure via 'current' is not recommended fo…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 30.3 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the CISA ADP record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 15.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.2%
0.2% → 0.2%
In the Linux kernel, the following vulnerability has been resolved:
sctp: sysctl: rto_min/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 reader's/writer's netns vs only from the opener's netns.
current->nsproxy can be NULL in some cases, resulting in an 'Oops' (null-ptr-deref), e.g. when the current task is exiting, as spotted by syzbot [1] using acct(2).
The 'net' structure can be obtained from the table->data using container_of().
Note that table->data could also be used directly, as this is the only member needed from the 'net' structure, but that would increase the size of this fix, to use '*data' everywhere 'net->sctp.rto_min/max' is used.
Linux >= 4f3fdf3bc59cafd14c3bc2c2369efad34c7aa8b5 < c8d179f3b1c1d60bf4484f50aa67b4c70f91bff9Linux >= 4f3fdf3bc59cafd14c3bc2c2369efad34c7aa8b5 < 246428bfb9e7db15c5cd08e1d0eca41b65af2b06Linux >= 4f3fdf3bc59cafd14c3bc2c2369efad34c7aa8b5 < 0f78f09466744589e420935e646ae78212a38290Linux >= 4f3fdf3bc59cafd14c3bc2c2369efad34c7aa8b5 < 4059507e34aa5fe0fa9fd5b2b5f0c8b26ab2d482Linux >= 4f3fdf3bc59cafd14c3bc2c2369efad34c7aa8b5 < dc9d0e3cfd16f66fbf0862857c6b391c8613ca9fLinux >= 4f3fdf3bc59cafd14c3bc2c2369efad34c7aa8b5 < c87f1f6ade56c711f8736901e330685b453e420eLinux >= 4f3fdf3bc59cafd14c3bc2c2369efad34c7aa8b5 < 9fc17b76fc70763780aa78b38fcf4742384044a5Linux 3.13Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets