Review reviewHigh

CVE-2025-38579

Linux Linux, linux kernel, debian linux

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix KMSAN uninit-value in extent_info usage KMSAN reported a use of uninitialized value in `__is_extent_mergeable()` and `__is_back_mergeable()` via the read extent tree path. The root cause is that `get_read_extent_info()` only initializes three fields (`fofs`, `blk`, `len`) of `struct extent_info`, leaving the remaining fields uninitialized. This leads to undefined behavior when those fields are accessed later, especially during extent merging. Fix it by zero-initializing the `extent_info` struct before population.

CVSS
7.8
EPSS
0.16%
6.06% percentile
CISA KEV
Not listed
Published
2025.08.20
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.16%
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix KMSAN uninit-value in extent_info usage KMSAN reported a use of uninitialized value in `__is_extent_mergeable()` and `__is_back_mergeable()` via the read extent tree path. The root cause is that `get_read_extent_info()` only initializes three fields (`fofs`, `blk`, `len`) of `struct extent_info`, leaving the remaining fields uninitialized. This leads to undefined behavior when those fields are accessed later, especially during extent merging. Fix it by zero-initializing the `extent_info` struct before population.

Affected product and versions

Product
Linux Linux, linux kernel, debian linux
Affected versions
>= 94afd6d6e5253179c9b891d02081cc8355a11768 < 08e8ab00a6d20d5544c932ee85a297d833895141, >= 94afd6d6e5253179c9b891d02081cc8355a11768 < e68b751ec2b15d866967812c57cfdfc1eba6a269, >= 94afd6d6e5253179c9b891d02081cc8355a11768 < dabfa3952c8e6bfe6414dbf32e8b6c5f349dc898, >= 94afd6d6e5253179c9b891d02081cc8355a11768 < 44a79437309e0ee2276ac17aaedc71253af253a8, >= 94afd6d6e5253179c9b891d02081cc8355a11768 < cc1615d5aba4f396cf412579928539a2b124c8a0, >= 94afd6d6e5253179c9b891d02081cc8355a11768 < 01b6f5955e0008af6bc3a181310d2744bb349800, >= 94afd6d6e5253179c9b891d02081cc8355a11768 < 154467f4ad033473e5c903a03e7b9bca7df9a0fa, >= 5.15, >= 5.15 < 5.15.190, >= 5.16 < 6.1.148, >= 6.2 < 6.6.102, >= 6.7 < 6.12.42, >= 6.13 < 6.15.10, >= 6.16 < 6.16.1, 11.0
Fixed versions
5.15.190, 6.1.148, 6.6.102, 6.12.42, 6.15.10, 6.16.1

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel, debian linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-908
CVE-2025-38579 — Linux Linux, linux kernel, debian linux | SECUFOCUS NOW