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

Vulnerability in Linux kernel

CVE-2024-50099 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-50099 has been found in Linux kernel.
Confidential information can be exposed externally. CVSS score: 7.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Linux kernel CVE-2024-50099" on the vendor's site.

CVE-2024-50099 (Linux kernel) — CVSS v3 7.3
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.3/10). Confidential information can be exposed externally.

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.10.0, < 4.19.323
≥ 4.20.0, < 5.4.285
≥ 5.5.0, < 5.10.228
≥ 5.11.0, < 5.15.169
≥ 5.16.0, < 6.1.114
≥ 6.2.0, < 6.6.58
+1 more
4.19.323
5.4.285
5.10.228
5.15.169
6.1.114
6.6.58

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:

arm64: probes: Remove broken LDR (literal) uprobe support

The simulate_ldr_literal() and simulate_ldrsw_literal() functions are
unsafe to use for uprobes. Both functions were originally written for
use with kprobes, and access memory with plain C accesses. When uprobes
was added, these were reused unmodified even though they cannot safely
access user memory.

There are three key problems:

  1. The plain C accesses do not have corresponding extable entries, and
    thus if they encounter a fault the kernel will treat these as
    unintentional accesses to user memory, resulting in a BUG() which
    will kill the kernel thread, and likely lead to further issues (e.g.
    lockup or panic()).

  2. The plain C accesses are subject to HW PAN and SW PAN, and so when
    either is in use, any attempt to simulate an access to user memory
    will fault. Thus neither simulate_ldr_literal() nor
    simulate_ldrsw_literal() can do anything useful when simulating a
    user instruction on any system with HW PAN or SW PAN.

  3. The plain C accesses are privileged, as they run in kernel context,
    and in practice can access a small range of kernel virtual addresses.
    The instructions they simulate have a range of +/-1MiB, and since the
    simulated instructions must itself be a user instructions in the
    TTBR0 address range, these can address the final 1MiB of the TTBR1
    acddress range by wrapping downwards from an address in…

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