SECUFOCUSNOW
Home›CVE index›CVE-2024-41070
Review reviewHigh

CVE-2024-41070

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: KVM: PPC: Book3S HV: Prevent UAF in kvm_spapr_tce_attach_iommu_group() Al reported a possible use-after-free (UAF) in kvm_spapr_tce_attach_iommu_group(). It looks up `stt` from tablefd, but then continues to use it after doing fdput() on the returned fd. After the fdput() the tablefd is free to be closed by another thread. The close calls kvm_spapr_tce_release() and then release_spapr_tce_table() (via call_rcu()) which frees `stt`. Although there are calls to rcu_read_lock() in kvm_spapr_tce_attach_iommu_group() they are no...

CVSS
7.8
EPSS
0.22%
13.2% percentile
CISA KEV
Not listed
Published
2024.07.30
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

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

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: KVM: PPC: Book3S HV: Prevent UAF in kvm_spapr_tce_attach_iommu_group() Al reported a possible use-after-free (UAF) in kvm_spapr_tce_attach_iommu_group(). It looks up `stt` from tablefd, but then continues to use it after doing fdput() on the returned fd. After the fdput() the tablefd is free to be closed by another thread. The close calls kvm_spapr_tce_release() and then release_spapr_tce_table() (via call_rcu()) which frees `stt`. Although there are calls to rcu_read_lock() in kvm_spapr_tce_attach_iommu_group() they are no...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 121f80ba68f1a5779a36d7b3247206e60e0a7418 < be847bb20c809de8ac124431b556f244400b0491, >= 121f80ba68f1a5779a36d7b3247206e60e0a7418 < 4cdf6926f443c84f680213c7aafbe6f91a5fcbc0, >= 121f80ba68f1a5779a36d7b3247206e60e0a7418 < b26c8c85463ef27a522d24fcd05651f0bb039e47, >= 121f80ba68f1a5779a36d7b3247206e60e0a7418 < 5f856023971f97fff74cfaf21b48ec320147b50a, >= 121f80ba68f1a5779a36d7b3247206e60e0a7418 < 82c7a4cf14aa866f8f7f09e662b02eddc49ee0bf, >= 121f80ba68f1a5779a36d7b3247206e60e0a7418 < 9975f93c760a32453d7639cf6fcf3f73b4e71ffe, >= 121f80ba68f1a5779a36d7b3247206e60e0a7418 < a986fa57fd81a1430e00b3c6cf8a325d6f894a63, >= 4.12, < 5.4.281, >= 5.5 < 5.10.223, >= 5.11 < 5.15.164, >= 5.16 < 6.1.101, >= 6.2 < 6.6.42, >= 6.7 < 6.9.11
Fixed versions
5.4.281, 5.10.223, 5.15.164, 6.1.101, 6.6.42, 6.9.11

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