Review reviewHigh

CVE-2024-41087

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: ata: libata-core: Fix double free on error If e.g. the ata_port_alloc() call in ata_host_alloc() fails, we will jump to the err_out label, which will call devres_release_group(). devres_release_group() will trigger a call to ata_host_release(). ata_host_release() calls kfree(host), so executing the kfree(host) in ata_host_alloc() will lead to a double free: kernel BUG at mm/slub.c:553! Oops: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI CPU: 11 PID: 599 Comm: (udev-worker) Not tainted 6.10.0-rc5 #47 Hardware name: QEMU Standa...

CVSS
7.8
EPSS
0.24%
15.6% 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.24%
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: ata: libata-core: Fix double free on error If e.g. the ata_port_alloc() call in ata_host_alloc() fails, we will jump to the err_out label, which will call devres_release_group(). devres_release_group() will trigger a call to ata_host_release(). ata_host_release() calls kfree(host), so executing the kfree(host) in ata_host_alloc() will lead to a double free: kernel BUG at mm/slub.c:553! Oops: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI CPU: 11 PID: 599 Comm: (udev-worker) Not tainted 6.10.0-rc5 #47 Hardware name: QEMU Standa...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= dafd6c496381c1cd1f5ba9ad953e810bdcc931bc < 290073b2b557e4dc21ee74a1e403d9ae79e393a2, >= dafd6c496381c1cd1f5ba9ad953e810bdcc931bc < 56f1c7e290cd6c69c948fcd2e2a49e6a637ec38f, >= dafd6c496381c1cd1f5ba9ad953e810bdcc931bc < 010de9acbea58fbcbda08e3793d6262086a493fe, >= dafd6c496381c1cd1f5ba9ad953e810bdcc931bc < 5dde5f8b790274723640d29a07c5a97d57d62047, >= dafd6c496381c1cd1f5ba9ad953e810bdcc931bc < 702c1edbafb2e6f9d20f6d391273b5be09d366a5, >= dafd6c496381c1cd1f5ba9ad953e810bdcc931bc < 062e256516d7db5e7dcdef117f52025cd5c456e3, >= dafd6c496381c1cd1f5ba9ad953e810bdcc931bc < 8106da4d88bbaed809e023cc8014b766223d6e76, >= dafd6c496381c1cd1f5ba9ad953e810bdcc931bc < ab9e0c529eb7cafebdd31fe1644524e80a48b05d, >= 4.17, >= 4.17 < 4.19.317, >= 4.20 < 5.4.279, >= 5.5 < 5.10.221, >= 5.11 < 5.15.162, >= 5.16 < 6.1.97, >= 6.2 < 6.6.37, >= 6.7 < 6.9.8
Fixed versions
4.19.317, 5.4.279, 5.10.221, 5.15.162, 6.1.97, 6.6.37, 6.9.8

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