Skip to main content
VulnerabilityPublished Updated

CVE-2025-38465: Linux kernel · netlink: Fix wraparounds of sk->sk_rmem_alloc.

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in fd69af06101090eaa60b3d216ae715f9c0a58e5b : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:19 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in fd69af06101090eaa60b3d216ae715f9c0a58e5b, cd7ff61bfffd7000143c42bbffb85eeb792466d6, c4ceaac5c5ba0b992ee1dc88e2a02421549e5c98 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < fd69af06101090eaa60b3d216ae715f9c0a58e5b
Fixed in
  • fd69af06101090eaa60b3d216ae715f9c0a58e5b
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < cd7ff61bfffd7000143c42bbffb85eeb792466d6
Fixed in
  • cd7ff61bfffd7000143c42bbffb85eeb792466d6
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < c4ceaac5c5ba0b992ee1dc88e2a02421549e5c98
Fixed in
  • c4ceaac5c5ba0b992ee1dc88e2a02421549e5c98
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < ae8f160e7eb24240a2a79fc4c815c6a0d4ee16cc
Fixed in
  • ae8f160e7eb24240a2a79fc4c815c6a0d4ee16cc
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 76602d8e13864524382b0687dc32cd8f19164d5a
Fixed in
  • 76602d8e13864524382b0687dc32cd8f19164d5a
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 55baecb9eb90238f60a8350660d6762046ebd3bd
Fixed in
  • 55baecb9eb90238f60a8350660d6762046ebd3bd

Description

In the Linux kernel, the following vulnerability has been resolved: netlink: Fix wraparounds of sk->sk_rmem_alloc. Netlink has this pattern in some places if (atomic_read(&sk->sk_rmem_alloc) > sk->sk_rcvbuf) atomic_add(skb->truesize, &sk->sk_rmem_alloc); , which has the same problem fixed by commit 5a465a0da13e ("udp: Fix multiple wraparounds of sk->sk_rmem_alloc."). For example, if we set INT_MAX to SO_RCVBUFFORCE, the condition is always false as the two operands are of int. Then, a single socket can eat as many skb as possible until OOM happens, and we can see multiple wraparounds of sk->sk_rmem_alloc. Let's fix it by using atomic_add_return() and comparing the two variables as unsigned int. Before: [root@fedora ~]# ss -f netlink Recv-Q Send-Q Local Address:Port Peer Address:Port -1668710080 0 rtnl:nl_wraparound/293 * After: [root@fedora ~]# ss -f netlink Recv-Q Send-Q Local Address:Port Peer Address:Port 2147483072 0 rtnl:nl_wraparound/290 * ^ `--- INT_MAX - 576

References

Community reviews

Loading reviews…