← Back
CVE-2025-40251
medium
CVSS 5.5
Vulnerability in c (CVE-2025-40251)
Summary
vulnerability in c (CVE-2025-40251). Risk of unauthorized operations or information disclosure. Exploitable via ``rate_leaf_parent_set``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-40251** has been found in c.
Attackers can target a specific entry point like ``rate_leaf_parent_set`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "c CVE-2025-40251" on the vendor's site.
CVE-2025-40251 (c) — CWE-476 / CVSS v3 5.5
Attack vector: local / no user interaction
Attack surface: `rate_leaf_parent_set` / `rate_node_parent_set` / `devlink_rate` / `devlink_nl_rate_parent_node_set`
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-476) exists in c. Attackers reach the vulnerable code path via ``rate_leaf_parent_set`` without authentication.
📍 Affected scope
c — . Attack surface: `rate_leaf_parent_set` / `rate_node_parent_set` / `devlink_rate` / `devlink_nl_rate_parent_node_set`.
🔥 Severity
Severity: Medium (CVSS 5.5/10). Risk of unauthorized operations or information disclosure
🔧 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 'c' .` 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 'c' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `c` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
References
- web https://git.kernel.org/stable/c/542f45486f1ce2d2dde75bd85aca0389ef7046c3
- web https://git.kernel.org/stable/c/715d9cda646a8a38ea8b2bb5afb679a7464055e2
- web https://git.kernel.org/stable/c/90e51e20bcec9bff5b2421ce1bd95704764655f5
- web https://git.kernel.org/stable/c/c70df6c17d389cc743f0eb30160e2d6bc6910db8
- web https://git.kernel.org/stable/c/f94c1a114ac209977bdf5ca841b98424295ab1f0
- web https://cert-portal.siemens.com/productcert/html/ssa-253495.html
- web https://nvd.nist.gov/vuln/detail/CVE-2025-40251
- web https://github.com/advisories/GHSA-4fxr-v6jm-9j9m