Skip to content
Fencer Vulns
medium 5.5

CVE-2021-47249 json

net: rds: fix memory leak in rds_recvmsg

published 2024-05-21 2 y ago modified 2026-06-17 4 mo ago also EUVD-2021-33897

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 14%
public exploits
0
none known

Summary

In the Linux kernel, the following vulnerability has been resolved:

net: rds: fix memory leak in rds_recvmsg

Syzbot reported memory leak in rds. The problem was in unputted refcount in case of error.

int rds_recvmsg(struct socket *sock, struct msghdr *msg, size_t size, int msg_flags) { ...

if (!rds_next_incoming(rs, &inc)) { ... }

After this "if" inc refcount incremented and

if (rds_cmsg_recv(inc, msg, rs)) { ret = -EFAULT; goto out; } ... out: return ret; }

in case of rds_cmsg_recv() fail the refcount won't be decremented. And it's easy to see from ftrace log, that rds_inc_addref() don't have rds_inc_put() pair in rds_recvmsg() after rds_cmsg_recv()

1) | rds_recvmsg() { 1) 3.721 us | rds_inc_addref(); 1) 3.853 us | rds_message_inc_copy_to_user(); 1) + 10.395 us | rds_cmsg_recv(); 1) + 34.260 us | }

Patch / fix

  • Linux Linux 4.4.274, 4.9.274, 4.14.238, 4.19.196, 5.4.128, 5.10.46, 5.12.13, 5.13
  • linux Debian 14, Debian 13, Debian 12 5.10.46-1

debian advisories DEBIAN-CVE-2021-47249

  • linux Ubuntu 18.04 LTS 4.15.0-156.163
  • linux Ubuntu 20.04 LTS 5.4.0-81.91
  • linux-aws Ubuntu 18.04 LTS 4.15.0-1111.118
  • linux-aws Ubuntu 20.04 LTS 5.4.0-1055.58
  • linux-gcp Ubuntu 20.04 LTS 5.4.0-1051.55
  • linux-kvm Ubuntu 18.04 LTS 4.15.0-1099.101
  • linux-kvm Ubuntu 20.04 LTS 5.4.0-1045.47
  • linux-azure Ubuntu 20.04 LTS 5.4.0-1056.58

ubuntu advisories UBUNTU-CVE-2021-47249

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-syms SLES for SAP 12 SP5, SLES 12 SP5 4.12.14-122.219.1
  • kernel-source SLES for SAP 12 SP5, SLES 12 SP5 4.12.14-122.219.1
  • kernel-default SLES for SAP 12 SP5, SLES 12 SP5, SLE Workstation Extension 12 SP5 +2 more 4.12.14-122.219.1
  • kernel-obs-build SLE Software Development Kit 12 SP5 4.12.14-122.219.1
  • kernel-rt SLE Real Time 12 SP5 4.12.14-10.188.1
  • kernel-syms-rt SLE Real Time 12 SP5 4.12.14-10.188.1
  • kernel-rt_debug SLE Real Time 12 SP5 4.12.14-10.188.1
  • kernel-source-rt SLE Real Time 12 SP5 4.12.14-10.188.1

suse advisories SUSE-SU-2024:2184-1SUSE-SU-2024:1983-1SUSE-SU-2024:1979-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2021-47249 updated cvss 6.1

kernel: net: rds: fix memory leak in rds_recvmsg

  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.24% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Linux Linux

Classification

Weakness
  • CWE-401 Missing Release of Memory after Effective Lifetime
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.