SECUFOCUSNOW
Home›CVE index›CVE-2021-47078
Review reviewHigh

CVE-2021-47078

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Clear all QP fields if creation failed rxe_qp_do_cleanup() relies on valid pointer values in QP for the properly created ones, but in case rxe_qp_from_init() failed it was filled with garbage and caused tot the following error. refcount_t: underflow; use-after-free. WARNING: CPU: 1 PID: 12560 at lib/refcount.c:28 refcount_warn_saturate+0x1d1/0x1e0 lib/refcount.c:28 Modules linked in: CPU: 1 PID: 12560 Comm: syz-executor.4 Not tainted 5.12.0-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute En...

CVSS
7.8
EPSS
0.28%
20.3% percentile
CISA KEV
Not listed
Published
2024.03.02
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.28%
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Clear all QP fields if creation failed rxe_qp_do_cleanup() relies on valid pointer values in QP for the properly created ones, but in case rxe_qp_from_init() failed it was filled with garbage and caused tot the following error. refcount_t: underflow; use-after-free. WARNING: CPU: 1 PID: 12560 at lib/refcount.c:28 refcount_warn_saturate+0x1d1/0x1e0 lib/refcount.c:28 Modules linked in: CPU: 1 PID: 12560 Comm: syz-executor.4 Not tainted 5.12.0-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute En...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 8700e3e7c4857d28ebaa824509934556da0b3e76 < c65391dd9f0a47617e96e38bd27e277cbe1c40b0, >= 8700e3e7c4857d28ebaa824509934556da0b3e76 < 6a8086a42dfbf548a42bf2ae4faa291645c72c66, >= 8700e3e7c4857d28ebaa824509934556da0b3e76 < f3783c415bf6d2ead3d7aa2c38802bbe10723646, >= 8700e3e7c4857d28ebaa824509934556da0b3e76 < a62225d951d77eb20208fed8fc199e0c9b1df08b, >= 8700e3e7c4857d28ebaa824509934556da0b3e76 < 2ee4d79c364914989c80de382c0b1a7259a7e4b3, >= 8700e3e7c4857d28ebaa824509934556da0b3e76 < 03344e843ab6dd3b3f2cadfb65ed910590856c70, >= 8700e3e7c4857d28ebaa824509934556da0b3e76 < 67f29896fdc83298eed5a6576ff8f9873f709228, >= 4.8, >= 4.8 < 4.9.270, >= 4.10 < 4.14.234, >= 4.15 < 4.19.192, >= 4.20 < 5.4.122, >= 5.5 < 5.10.40, >= 5.11 < 5.12.7, 5.13
Fixed versions
4.9.270, 4.14.234, 4.19.192, 5.4.122, 5.10.40, 5.12.7

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-416