CVE-2024-46704 Vulnerability Analysis & Exploit Details

CVE-2024-46704
Vulnerability Scoring

4.7
/10
Medium Risk

The vulnerability CVE-2024-46704 could compromise system integrity but typically requires user interaction to be exploited.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and 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-46704 Details

Status: Analyzed

Last updated: 🕜 19 Sep 2024, 13:32 UTC
Originally published on: 🕖 13 Sep 2024, 07:15 UTC

Time between publication and last update: 6 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2024-46704 Vulnerability Summary

CVE-2024-46704: In the Linux kernel, the following vulnerability has been resolved: workqueue: Fix spruious data race in __flush_work() When flushing a work item for cancellation, __flush_work() knows that it exclusively owns the work item through its PENDING bit. 134874e2eee9 ("workqueue: Allow cancel_work_sync() and disable_work() from atomic contexts on BH work items") added a read of @work->data to determine whether to use busy wait for BH work items that are being canceled. While the read is safe when @from_cancel, @work->data was read before testing @from_cancel to simplify code structure: data = *work_data_bits(work); if (from_cancel && !WARN_ON_ONCE(data & WORK_STRUCT_PWQ) && (data & WORK_OFFQ_BH)) { While the read data was never used if !@from_cancel, this could trigger KCSAN data race detection spuriously: ================================================================== BUG: KCSAN: data-race in __flush_work / __flush_work write to 0xffff8881223aa3e8 of 8 bytes by task 3998 on cpu 0: instrument_write include/linux/instrumented.h:41 [inline] ___set_bit include/asm-generic/bitops/instrumented-non-atomic.h:28 [inline] insert_wq_barrier kernel/workqueue.c:3790 [inline] start_flush_work kernel/workqueue.c:4142 [inline] __flush_work+0x30b/0x570 kernel/workqueue.c:4178 flush_work kernel/workqueue.c:4229 [inline] ... read to 0xffff8881223aa3e8 of 8 bytes by task 50 on cpu 1: __flush_work+0x42a/0x570 kernel/workqueue.c:4188 flush_work kernel/workqueue.c:4229 [inline] flush_delayed_work+0x66/0x70 kernel/workqueue.c:4251 ... value changed: 0x0000000000400000 -> 0xffff88810006c00d Reorganize the code so that @from_cancel is tested before @work->data is accessed. The only problem is triggering KCSAN detection spuriously. This shouldn't need READ_ONCE() or other access qualifiers. No functional changes.

Assessing the Risk of CVE-2024-46704

Access Complexity Graph

The exploitability of CVE-2024-46704 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-46704

This vulnerability, CVE-2024-46704, requires a high level of attack complexity and low privileges, making it difficult but not impossible to exploit. Organizations should ensure robust security configurations to mitigate 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-46704, 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-46704, 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-46704 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2024-46704 poses no threat to data integrity.
  • Availability: High
    CVE-2024-46704 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.043% (probability of exploit)

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

CVE-2024-46704 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.11:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11:rc4:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2024-46704: 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...