Review reviewHigh

CVE-2024-47748

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: vhost_vdpa: assign irq bypass producer token correctly We used to call irq_bypass_unregister_producer() in vhost_vdpa_setup_vq_irq() which is problematic as we don't know if the token pointer is still valid or not. Actually, we use the eventfd_ctx as the token so the life cycle of the token should be bound to the VHOST_SET_VRING_CALL instead of vhost_vdpa_setup_vq_irq() which could be called by set_status(). Fixing this by setting up irq bypass producer's token when handling VHOST_SET_VRING_CALL and un-registering the produ...

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: vhost_vdpa: assign irq bypass producer token correctly We used to call irq_bypass_unregister_producer() in vhost_vdpa_setup_vq_irq() which is problematic as we don't know if the token pointer is still valid or not. Actually, we use the eventfd_ctx as the token so the life cycle of the token should be bound to the VHOST_SET_VRING_CALL instead of vhost_vdpa_setup_vq_irq() which could be called by set_status(). Fixing this by setting up irq bypass producer's token when handling VHOST_SET_VRING_CALL and un-registering the produ...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 2cf1ba9a4d15cb78b96ea97f727b93382c3f9a60 < 0c170b1e918b9afac25e2bbd01eaa2bfc0ece8c0, >= 2cf1ba9a4d15cb78b96ea97f727b93382c3f9a60 < 927a2580208e0f9b0b47b08f1c802b7233a7ba3c, >= 2cf1ba9a4d15cb78b96ea97f727b93382c3f9a60 < ec5f1b54ceb23475049ada6e7a43452cf4df88d1, >= 2cf1ba9a4d15cb78b96ea97f727b93382c3f9a60 < ca64edd7ae93402af2596a952e0d94d545e2b9c0, >= 2cf1ba9a4d15cb78b96ea97f727b93382c3f9a60 < fae9b1776f53aab93ab345bdbf653b991aed717d, >= 2cf1ba9a4d15cb78b96ea97f727b93382c3f9a60 < 7cf2fb51175cafe01df8c43fa15a06194a59c6e2, >= 2cf1ba9a4d15cb78b96ea97f727b93382c3f9a60 < 02e9e9366fefe461719da5d173385b6685f70319, >= 5.9, >= 5.9 < 5.10.227, >= 5.11 < 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.10.227, 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-416