CVE-2024-47724 Vulnerability Analysis & Exploit Details

CVE-2024-47724
Vulnerability Scoring

5.5
/10
Significant Risk

Security assessments indicate that CVE-2024-47724 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2024-47724 Details

Status: Analyzed

Last updated: 🕤 23 Oct 2024, 21:41 UTC
Originally published on: 🕐 21 Oct 2024, 13:15 UTC

Time between publication and last update: 2 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2024-47724 Vulnerability Summary

CVE-2024-47724: In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: use work queue to process beacon tx event Commit 3a415daa3e8b ("wifi: ath11k: add P2P IE in beacon template") from Feb 28, 2024 (linux-next), leads to the following Smatch static checker warning: drivers/net/wireless/ath/ath11k/wmi.c:1742 ath11k_wmi_p2p_go_bcn_ie() warn: sleeping in atomic context The reason is that ath11k_bcn_tx_status_event() will directly call might sleep function ath11k_wmi_cmd_send() during RCU read-side critical sections. The call trace is like: ath11k_bcn_tx_status_event() -> rcu_read_lock() -> ath11k_mac_bcn_tx_event() -> ath11k_mac_setup_bcn_tmpl() …… -> ath11k_wmi_bcn_tmpl() -> ath11k_wmi_cmd_send() -> rcu_read_unlock() Commit 886433a98425 ("ath11k: add support for BSS color change") added the ath11k_mac_bcn_tx_event(), commit 01e782c89108 ("ath11k: fix warning of RCU usage for ath11k_mac_get_arvif_by_vdev_id()") added the RCU lock to avoid warning but also introduced this BUG. Use work queue to avoid directly calling ath11k_mac_bcn_tx_event() during RCU critical sections. No need to worry about the deletion of vif because cancel_work_sync() will drop the work if it doesn't start or block vif deletion until the running work is done. Tested-on: WCN6855 hw2.0 PCI WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.30

Assessing the Risk of CVE-2024-47724

Access Complexity Graph

The exploitability of CVE-2024-47724 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2024-47724

CVE-2024-47724 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2024-47724, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2024-47724, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2024-47724 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2024-47724 poses no threat to data integrity.
  • Availability: High
    CVE-2024-47724 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.042% (probability of exploit)

EPSS Percentile: 5.02% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 94.98% of others.

CVE-2024-47724 References

External References

CWE Common Weakness Enumeration

NVD-CWE-noinfo

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:6.10:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11:-:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2024-47724: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...
  • CVE-2025-2125 – A vulnerability has been found in Control iD RH iD 25.2.25.0 and classified as problematic. This vulnerability affects unknown code of the file /v2...
  • CVE-2025-2124 – A vulnerability, which was classified as problematic, was found in Control iD RH iD 25.2.25.0. This affects an unknown part of the file /v2/custome...