Categories
CVE-2024-47741 high CVSS 7.8

Vulnerability in Linux kernel (CVE-2024-47741)

Summary

Vulnerability in Linux kernel (CVE-2024-47741). 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 setting file private on concurrent lseek using same fd

When doing concurrent lseek(2) system calls against the same file
descriptor, using multiple threads belonging to the same process, we have
a short time window where a race happens and can result in a memory leak.

The race happens like this:

  1. A program opens a file descriptor for a file and then spawns two
    threads (with the pthreads library for example), lets call them
    task A and task B;

  2. Task A calls lseek with SEEK_DATA or SEEK_HOLE and ends up at
    file.c:find_desired_extent() while holding a read lock on the inode;

  3. At the start of find_desired_extent(), it extracts the file's
    private_data pointer into a local variable named 'private', which has
    a value of NULL;

  4. Task B also calls lseek with SEEK_DATA or SEEK_HOLE, locks the inode
    in shared mode and enters file.c:find_desired_extent(), where it also
    extracts file->private_data into its local variable 'private', which
    has a NULL value;

  5. Because it saw a NULL file private, task A allocates a private
    structure and assigns to the file structure;

  6. Task B also saw a NULL file private so it also allocates its own file
    private and then assigns it to the same file structure, since both
    tasks are using the same file descriptor.

    At this point we leak the private structure allocated by task A.

Besides the memory leak, there's also the detail…

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-47741 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-47741" on the vendor's site.

CVE-2024-47741 (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":"6.2.0"},{"fixed":"6.6.54"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.10.13"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.11.0"},{"fixed":"6.11.2"}]}]

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