Review reviewHigh

CVE-2024-47695

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds In the function init_conns(), after the create_con() and create_cm() for loop if something fails. In the cleanup for loop after the destroy tag, we access out of bound memory because cid is set to clt_path->s.con_num. This commits resets the cid to clt_path->s.con_num - 1, to stay in bounds in the cleanup loop later.

CVSS
7.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2024.10.21
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds In the function init_conns(), after the create_con() and create_cm() for loop if something fails. In the cleanup for loop after the destroy tag, we access out of bound memory because cid is set to clt_path->s.con_num. This commits resets the cid to clt_path->s.con_num - 1, to stay in bounds in the cleanup loop later.

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 6a98d71daea186247005099758af549e6afdd244 < 0429a4e972082e3a2351da414b1c017daaf8aed2, >= 6a98d71daea186247005099758af549e6afdd244 < 5ac73f8191f3de41fef4f934d84d97f3aadb301f, >= 6a98d71daea186247005099758af549e6afdd244 < 01b9be936ee8839ab9f83a7e84ee02ac6c8303c4, >= 6a98d71daea186247005099758af549e6afdd244 < 1c50e0265fa332c94a4a182e4efa0fc70d8fad94, >= 6a98d71daea186247005099758af549e6afdd244 < c8b7f3d9fada0d4b4b7db86bf7345cd61f1d972e, >= 6a98d71daea186247005099758af549e6afdd244 < 3e4289b29e216a55d08a89e126bc0b37cbad9f38, >= 5.8, >= 5.8 < 5.15.168, >= 5.16 < 6.1.113, >= 6.2 < 6.6.54, >= 6.7 < 6.10.13, >= 6.11 < 6.11.2
Fixed versions
5.15.168, 6.1.113, 6.6.54, 6.10.13, 6.11.2

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-787