netlink: Fix wraparounds of sk->sk_rmem_alloc.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.4.296, 5.10.240, 5.15.189, 6.1.146, 6.6.99, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 9da025150b7c14a8390fc06aea314c0a4011e82c; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in c4ceaac5c5ba0b992ee1dc88e2a02421549e5c98; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in fd69af06101090eaa60b3d216ae715f9c0a58e5b; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 76602d8e13864524382b0687dc32cd8f19164d5a; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 55baecb9eb90238f60a8350660d6762046ebd3bd; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 4b8e18af7bea92f8b7fb92d40aeae729209db250; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in cd7ff61bfffd7000143c42bbffb85eeb792466d6; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in ae8f160e7eb24240a2a79fc4c815c6a0d4ee16cc
- Linux Linux
2.6.12
- KernelLinux
From 2.6.12 · fixed in 5.4.296; From 5.5.0 · fixed in 5.10.240; From 5.11.0 · fixed in 5.15.189; From 5.16.0 · fixed in 6.1.146; From 6.2.0 · fixed in 6.6.99; From 6.7.0 · fixed in 6.12.39; From 6.13.0 · fixed in 6.15.7
References 8
git.kernel.org
- stable/c/9da025150b7c14a8390fc06aea314c0a4011e82c
- stable/c/c4ceaac5c5ba0b992ee1dc88e2a02421549e5c98
- stable/c/fd69af06101090eaa60b3d216ae715f9c0a58e5b
- stable/c/76602d8e13864524382b0687dc32cd8f19164d5a
- stable/c/55baecb9eb90238f60a8350660d6762046ebd3bd
- stable/c/4b8e18af7bea92f8b7fb92d40aeae729209db250
- stable/c/cd7ff61bfffd7000143c42bbffb85eeb792466d6
- stable/c/ae8f160e7eb24240a2a79fc4c815c6a0d4ee16cc