Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2024-46734 high CVSS 7.8

Vulnerability in Linux kernel (CVE-2024-46734)

Summary

Vulnerability in Linux kernel (CVE-2024-46734). Successful exploitation can lead to full system takeover.

Original description

The description as published by the source.

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 p…

Source: NIST National Vulnerability Database NVD

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2024-46734 has been found in Linux kernel.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Linux kernel CVE-2024-46734" on the vendor's site.

CVE-2024-46734 (Linux kernel) — CWE-362 / CVSS v3 7.8
Attack vector: local / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-362) exists in Linux kernel.

📍 Affected scope

Check the vendor advisory for the affected versions of Linux kernel.

🔥 Severity

Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Linux kernel を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Linux Kernel
[{"type":"ECOSYSTEM","events":[{"introduced":"5.15.165"},{"fixed":"5.15.167"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.1.105"},{"fixed":"6.1.110"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.6.46"},{"fixed":"6.6.51"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.10.5"},{"fixed":"6.10.10"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details