Skip to content
Fencer Vulns
high 8.4

CVE-2021-47240 json

net: qrtr: fix OOB Read in qrtr_endpoint_post

published 2024-05-21 2 y ago modified 2026-08-05 3 mo ago also EUVD-2021-33888

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

Summary

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

net: qrtr: fix OOB Read in qrtr_endpoint_post

Syzbot reported slab-out-of-bounds Read in qrtr_endpoint_post. The problem was in wrong _size_ type:

if (len != ALIGN(size, 4) + hdrlen) goto err;

If size from qrtr_hdr is 4294967293 (0xfffffffd), the result of ALIGN(size, 4) will be 0. In case of len == hdrlen and size == 4294967293 in header this check won't fail and

skb_put_data(skb, data + hdrlen, size);

will read out of bound from data, which is hdrlen allocated block.

Patch / fix

  • Linux Linux 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-47240

  • 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-47240

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-rt SLE Micro 5.2, SLE Micro 5.1 5.3.18-150300.211.1
  • kernel-source-rt SLE Micro 5.2, SLE Micro 5.1 5.3.18-150300.211.1
  • kernel-64kb SLES 15 SP3-LTSS, SLE High Performance Computing 15 SP3-LTSS, Enterprise Storage 7.1 5.3.18-150300.59.164.1
  • kernel-syms SLES for SAP 15 SP3, SLES 15 SP3-LTSS, SLE High Performance Computing 15 SP3-LTSS +1 more 5.3.18-150300.59.164.1
  • kernel-source SLES for SAP 15 SP3, SLES 15 SP3-LTSS, SLE High Performance Computing 15 SP3-LTSS +1 more 5.3.18-150300.59.164.1
  • kernel-default SLES for SAP 15 SP3, SLES 15 SP3-LTSS, SLE Micro 5.2 +5 more 5.3.18-150300.59.164.1
  • kernel-preempt SLES for SAP 15 SP3, SLES 15 SP3-LTSS, SLE High Performance Computing 15 SP3-LTSS +1 more 5.3.18-150300.59.164.1
  • kernel-obs-build SLES for SAP 15 SP3, SLES 15 SP3-LTSS, SLE High Performance Computing 15 SP3-LTSS +1 more 5.3.18-150300.59.164.1

suse advisories SUSE-SU-2025:01995-1SUSE-SU-2024:2185-1SUSE-SU-2024:2183-1SUSE-SU-2024:2010-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-47240 updated cvss 6.1

kernel: net: qrtr: fix OOB Read in qrtr_endpoint_post

  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more 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 15% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Affected products

  • Linux Linux

Classification

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