← Back
CVE-2024-50121
high
CVSS 7.8
Use-After-Free in linux (CVE-2024-50121)
Summary
vulnerability in linux (CVE-2024-50121). Successful exploitation can lead to full system takeover. Exploitable via ``nfs4_state_destroy_net``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-50121** has been found in linux.
Attackers can target a specific entry point like ``nfs4_state_destroy_net`` over the network to misuse the product.
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 CVE-2024-50121" on the vendor's site.
CVE-2024-50121 (linux) — CWE-416 / CVSS v3 7.8
Attack vector: local / no user interaction
Attack surface: `nfs4_state_destroy_net` / `nfs4_state_shutdown_net` / `nfs4_client` / `nfsd_client_shrinker`
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. Attackers reach the vulnerable code path via ``nfs4_state_destroy_net`` without authentication.
📍 Affected scope
linux — . Attack surface: `nfs4_state_destroy_net` / `nfs4_state_shutdown_net` / `nfs4_client` / `nfsd_client_shrinker`.
🔥 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. Run `grep -r 'linux' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'linux' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `linux` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
References
- web https://git.kernel.org/stable/c/36775f42e039b01d4abe8998bf66771a37d3cdcc
- web https://git.kernel.org/stable/c/5ade4382de16c34d9259cb548f36ec5c4555913c
- web https://git.kernel.org/stable/c/add1df5eba163a3a6ece11cb85890e2e410baaea
- web https://git.kernel.org/stable/c/d5ff2fb2e7167e9483846e34148e60c0c016a1f6
- web https://git.kernel.org/stable/c/f67138dd338cb564ade7d3755c8cd4f68b46d397
- web https://git.kernel.org/stable/c/f965dc0f099a54fca100acf6909abe52d0c85328
- web https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html
- web https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html
- web https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- web https://nvd.nist.gov/vuln/detail/CVE-2024-50121
- web https://github.com/advisories/GHSA-wrcm-3w95-9w36