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

Use-After-Free in Linux kernel (CVE-2024-41010)

Summary

Vulnerability in Linux kernel (CVE-2024-41010). 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:

bpf: Fix too early release of tcx_entry

Pedro Pinto and later independently also Hyunwoo Kim and Wongi Lee reported
an issue that the tcx_entry can be released too early leading to a use
after free (UAF) when an active old-style ingress or clsact qdisc with a
shared tc block is later replaced by another ingress or clsact instance.

Essentially, the sequence to trigger the UAF (one example) can be as follows:

  1. A network namespace is created

  2. An ingress qdisc is created. This allocates a tcx_entry, and
    &tcx_entry->miniq is stored in the qdisc's miniqp->p_miniq. At the
    same time, a tcf block with index 1 is created.

  3. chain0 is attached to the tcf block. chain0 must be connected to
    the block linked to the ingress qdisc to later reach the function
    tcf_chain0_head_change_cb_del() which triggers the UAF.

  4. Create and graft a clsact qdisc. This causes the ingress qdisc
    created in step 1 to be removed, thus freeing the previously linked
    tcx_entry:

    rtnetlink_rcv_msg()
    => tc_modify_qdisc()
    => qdisc_create()
    => clsact_init() [a]
    => qdisc_graft()
    => qdisc_destroy()
    => __qdisc_destroy()
    => ingress_destroy() [b]
    => tcx_entry_free()
    => kfree_rcu() // tcx_entry freed

  5. Finally, the network namespace is closed. This registers the
    cleanup_net worker, and du…

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

CVE-2024-41010 (Linux kernel) — CWE-416 / 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

Use-after-free (CWE-416) 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.6.0"},{"fixed":"6.6.41"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.9.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