Skip to content
Sign in Sign up
JA EN FR
SecPulse
High 7.8

Vulnerability in Linux kernel

CVE-2024-46787 First seen on SecPulse

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

CVE-2024-46787 (Linux kernel) — 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 (unclassified) 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 exposureidentify
    Audit SBOM/dependencies for affected components.

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

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

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

Affected packages

EcosystemPackageAffectedFixed
Linux Kernel
≥ 4.3.0, < 6.6.51
≥ 6.7.0, < 6.10.10
6.6.51
6.10.10

Fix status by distribution

Fixed packages published by each distribution for this CVE

Original description The description as published by the source.

In the Linux kernel, the following vulnerability has been resolved:

userfaultfd: fix checks for huge PMDs

Patch series "userfaultfd: fix races around pmd_trans_huge() check", v2.

The pmd_trans_huge() code in mfill_atomic() is wrong in three different
ways depending on kernel version:

  1. The pmd_trans_huge() check is racy and can lead to a BUG_ON() (if you hit
    the right two race windows) - I've tested this in a kernel build with
    some extra mdelay() calls. See the commit message for a description
    of the race scenario.
    On older kernels (before 6.5), I think the same bug can even
    theoretically lead to accessing transhuge page contents as a page table
    if you hit the right 5 narrow race windows (I haven't tested this case).
  2. As pointed out by Qi Zheng, pmd_trans_huge() is not sufficient for
    detecting PMDs that don't point to page tables.
    On older kernels (before 6.5), you'd just have to win a single fairly
    wide race to hit this.
    I've tested this on 6.1 stable by racing migration (with a mdelay()
    patched into try_to_migrate()) against UFFDIO_ZEROPAGE - on my x86
    VM, that causes a kernel oops in ptlock_ptr().
  3. On newer kernels (>=6.5), for shmem mappings, khugepaged is allowed
    to yank page tables out from under us (though I haven't tested that),
    so I think the BUG_ON() checks in mfill_atomic() are just wrong.

I decided to write two separate fixes for these (one fix for bugs 1+2, one
fix for bug 3), so that the first fix can be backpo…

Source: NIST National Vulnerability Database NVD

References

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