CVE-2024-46734 Vulnerability Analysis & Exploit Details

CVE-2024-46734
Vulnerability Scoring

4.7
/10
Medium Risk

The vulnerability CVE-2024-46734 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-46734 Details

Status: Analyzed

Last updated: 🕡 19 Sep 2025, 18:52 UTC
Originally published on: 🕗 18 Sep 2024, 08:15 UTC

Time between publication and last update: 366 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-46734 Vulnerability Summary

CVE-2024-46734: In the Linux kernel, the following vulnerability has been resolved: btrfs: fix race between direct IO write and fsync when using same fd If we have 2 threads that are using the same file descriptor and one of them is doing direct IO writes while the other is doing fsync, we have a race where we can end up either: 1) Attempt a fsync without holding the inode's lock, triggering an assertion failures when assertions are enabled; 2) Do an invalid memory access from the fsync task because the file private points to memory allocated on stack by the direct IO task and it may be used by the fsync task after the stack was destroyed. The race happens like this: 1) A user space program opens a file descriptor with O_DIRECT; 2) The program spawns 2 threads using libpthread for example; 3) One of the threads uses the file descriptor to do direct IO writes, while the other calls fsync using the same file descriptor. 4) Call task A the thread doing direct IO writes and task B the thread doing fsyncs; 5) Task A does a direct IO write, and at btrfs_direct_write() sets the file's private to an on stack allocated private with the member 'fsync_skip_inode_lock' set to true; 6) Task B enters btrfs_sync_file() and sees that there's a private structure associated to the file which has 'fsync_skip_inode_lock' set to true, so it skips locking the inode's VFS lock; 7) Task A completes the direct IO write, and resets the file's private to NULL since it had no prior private and our private was stack allocated. Then it unlocks the inode's VFS lock; 8) Task B enters btrfs_get_ordered_extents_for_logging(), then the assertion that checks the inode's VFS lock is held fails, since task B never locked it and task A has already unlocked it. The stack trace produced is the following: assertion failed: inode_is_locked(&inode->vfs_inode), in fs/btrfs/ordered-data.c:983 ------------[ cut here ]------------ kernel BUG at fs/btrfs/ordered-data.c:983! Oops: invalid opcode: 0000 [#1] PREEMPT SMP PTI CPU: 9 PID: 5072 Comm: worker Tainted: G U OE 6.10.5-1-default #1 openSUSE Tumbleweed 69f48d427608e1c09e60ea24c6c55e2ca1b049e8 Hardware name: Acer Predator PH315-52/Covini_CFS, BIOS V1.12 07/28/2020 RIP: 0010:btrfs_get_ordered_extents_for_logging.cold+0x1f/0x42 [btrfs] Code: 50 d6 86 c0 e8 (...) RSP: 0018:ffff9e4a03dcfc78 EFLAGS: 00010246 RAX: 0000000000000054 RBX: ffff9078a9868e98 RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffff907dce4a7800 RDI: ffff907dce4a7800 RBP: ffff907805518800 R08: 0000000000000000 R09: ffff9e4a03dcfb38 R10: ffff9e4a03dcfb30 R11: 0000000000000003 R12: ffff907684ae7800 R13: 0000000000000001 R14: ffff90774646b600 R15: 0000000000000000 FS: 00007f04b96006c0(0000) GS:ffff907dce480000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f32acbfc000 CR3: 00000001fd4fa005 CR4: 00000000003726f0 Call Trace: <TASK> ? __die_body.cold+0x14/0x24 ? die+0x2e/0x50 ? do_trap+0xca/0x110 ? do_error_trap+0x6a/0x90 ? btrfs_get_ordered_extents_for_logging.cold+0x1f/0x42 [btrfs bb26272d49b4cdc847cf3f7faadd459b62caee9a] ? exc_invalid_op+0x50/0x70 ? btrfs_get_ordered_extents_for_logging.cold+0x1f/0x42 [btrfs bb26272d49b4cdc847cf3f7faadd459b62caee9a] ? asm_exc_invalid_op+0x1a/0x20 ? btrfs_get_ordered_extents_for_logging.cold+0x1f/0x42 [btrfs bb26272d49b4cdc847cf3f7faadd459b62caee9a] ? btrfs_get_ordered_extents_for_logging.cold+0x1f/0x42 [btrfs bb26272d49b4cdc847cf3f7faadd459b62caee9a] btrfs_sync_file+0x21a/0x4d0 [btrfs bb26272d49b4cdc847cf3f7faadd459b62caee9a] ? __seccomp_filter+0x31d/0x4f0 __x64_sys_fdatasync+0x4f/0x90 do_syscall_64+0x82/0x160 ? do_futex+0xcb/0x190 ? __x64_sys_futex+0x10e/0x1d0 ? switch_fpu_return+0x4f/0xd0 ? syscall_exit_to_user_mode+0x72/0x220 ? do_syscall_64+0x8e/0x160 ? syscall_exit_to_user_mod ---truncated---

Assessing the Risk of CVE-2024-46734

Access Complexity Graph

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

This vulnerability, CVE-2024-46734, 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-46734, 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-46734, 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-46734 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2024-46734 poses no threat to data integrity.
  • Availability: High
    CVE-2024-46734 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.045% (probability of exploit)

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

CVE-2024-46734 References

External References

CWE Common Weakness Enumeration

CWE-362

CAPEC Common Attack Pattern Enumeration and Classification

  • Leveraging Race Conditions CAPEC-26 The adversary targets a race condition occurring when multiple processes access and manipulate the same resource concurrently, and the outcome of the execution depends on the particular order in which the access takes place. The adversary can leverage a race condition by "running the race", modifying the resource and modifying the normal execution flow. For instance, a race condition can occur while accessing a file: the adversary can trick the system by replacing the original file with their version and cause the system to read the malicious file.
  • Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions CAPEC-29 This attack targets a race condition occurring between the time of check (state) for a resource and the time of use of a resource. A typical example is file access. The adversary can leverage a file access race condition by "running the race", meaning that they would modify the resource between the first time the target program accesses the file and the time the target program uses the file. During that period of time, the adversary could replace or modify the file, causing the application to behave unexpectedly.

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:5.15.165:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.165:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.166:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.166:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.1.105:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.1.105:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.1.106:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.1.106:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.1.107:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.1.107:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.1.108:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.1.108:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.1.109:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.1.109:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.46:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.46:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.47:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.47:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.48:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.48:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.49:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.49:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.50:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.50:*:*:*:*:*:*:*
  • 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.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:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11:rc6:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11:rc6:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2024-46734: 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-62672 – rplay through 3.3.2 allows attackers to cause a denial of service (SIGSEGV and daemon crash) or possibly have unspecified other impact. This occurs...
  • CVE-2025-47410 – Apache Geode is vulnerable to CSRF attacks through GET requests to the Management and Monitoring REST API that could allow an attacker who has tric...
  • CVE-2025-11926 – The Related Posts Lite plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 1...
  • CVE-2025-9890 – The Theme Editor plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.0. This is due to missing...
  • CVE-2025-5555 – A vulnerability has been found in Nixdorf Wincor PORT IO Driver up to 1.0.0.1. This affects the function sub_11100 in the library wnport.sys of the...