Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2025-71183 critical CVSS 9.1

Vulnerability in Kernel (CVE-2025-71183)

Summary

Vulnerability in Kernel (CVE-2025-71183). Data can be tampered with by attackers. Mitigation: upgrade to 6.1.161, 6.6.121, 6.12.66, 6.18.6 or later.

Original description

The description as published by the source.

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

btrfs: always detect conflicting inodes when logging inode refs

After rename exchanging (either with the rename exchange operation or
regular renames in multiple non-atomic steps) two inodes and at least
one of them is a directory, we can end up with a log tree that contains
only of the inodes and after a power failure that can result in an attempt
to delete the other inode when it should not because it was not deleted
before the power failure. In some case that delete attempt fails when
the target inode is a directory that contains a subvolume inside it, since
the log replay code is not prepared to deal with directory entries that
point to root items (only inode items).

  1. We have directories "dir1" (inode A) and "dir2" (inode B) under the
    same parent directory;

  2. We have a file (inode C) under directory "dir1" (inode A);

  3. We have a subvolume inside directory "dir2" (inode B);

  4. All these inodes were persisted in a past transaction and we are
    currently at transaction N;

  5. We rename the file (inode C), so at btrfs_log_new_name() we update
    inode C's last_unlink_trans to N;

  6. We get a rename exchange for "dir1" (inode A) and "dir2" (inode B),
    so after the exchange "dir1" is inode B and "dir2" is inode A.
    During the rename exchange we call btrfs_log_new_name() for inodes
    A and B, but because they are directories, we don't update their
    last_unlink_trans to N;

  7. An fsync agains…

Source: OSV.dev (Open Source Vulnerabilities) NVD OSV

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-2025-71183 has been found in Kernel.
Data can be tampered with by attackers. CVSS score: 9.1/10.
What to do: upgrade Kernel to 6.1.161, 6.6.121, 6.12.66, 6.18.6 or later.
If unsure, ask your IT team or search "Kernel CVE-2025-71183" on the vendor's site.

CVE-2025-71183 (Kernel) — CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 6.1.161, 6.6.121, 6.12.66, 6.18.6 — apply immediately
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 Kernel.

📍 Affected scope

Check the vendor advisory for the affected versions of Kernel.

🔥 Severity

Severity: Critical (CVSS 9.1/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 6.1.161, 6.6.121, 6.12.66, 6.18.6.

🛡️ 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 'Kernel' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'Kernel' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Kernel を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade Kernel to 6.1.161, 6.6.121, 6.12.66, 6.18.6

    ステージング環境で 6.1.161, 6.6.121, 6.12.66, 6.18.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

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

Affected packages

Linux Kernel
[{"type":"ECOSYSTEM","events":[{"introduced":"4.6.0"},{"fixed":"6.1.161"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.121"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.66"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.6"}]}]

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