Review reviewHigh

CVE-2025-38230

Linux Linux, linux kernel, debian linux

In the Linux kernel, the following vulnerability has been resolved: jfs: validate AG parameters in dbMount() to prevent crashes Validate db_agheight, db_agwidth, and db_agstart in dbMount to catch corrupted metadata early and avoid undefined behavior in dbAllocAG. Limits are derived from L2LPERCTL, LPERCTL/MAXAG, and CTLTREESIZE: - agheight: 0 to L2LPERCTL/2 (0 to 5) ensures shift (L2LPERCTL - 2*agheight) >= 0. - agwidth: 1 to min(LPERCTL/MAXAG, 2^(L2LPERCTL - 2*agheight)) ensures agperlev >= 1. - Ranges: 1-8 (agheight 0-3), 1-4 (agheight 4), 1 (agheight 5). - LPERCTL/MAXAG = 1024/128 = 8 l...

CVSS
7.8
EPSS
0.16%
5.75% percentile
CISA KEV
Not listed
Published
2025.07.04
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: jfs: validate AG parameters in dbMount() to prevent crashes Validate db_agheight, db_agwidth, and db_agstart in dbMount to catch corrupted metadata early and avoid undefined behavior in dbAllocAG. Limits are derived from L2LPERCTL, LPERCTL/MAXAG, and CTLTREESIZE: - agheight: 0 to L2LPERCTL/2 (0 to 5) ensures shift (L2LPERCTL - 2*agheight) >= 0. - agwidth: 1 to min(LPERCTL/MAXAG, 2^(L2LPERCTL - 2*agheight)) ensures agperlev >= 1. - Ranges: 1-8 (agheight 0-3), 1-4 (agheight 4), 1 (agheight 5). - LPERCTL/MAXAG = 1024/128 = 8 l...

Affected product and versions

Product
Linux Linux, linux kernel, debian linux
Affected versions
>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 95ae5ee6069d9a5945772625f289422ef659221a, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < a4259e72363e1ea204a97292001a9fc36c7e52fd, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < c3705c82b7406a15ef38a610d03bf6baa43d6e0c, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 9242ff6245527a3ebb693ddd175493b38ddca72f, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 0c40fa81f850556e9aa0185fede9ef1112db7b39, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 8b69608c6b6779a7ab07ce4467a56df90152cfb9, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < b62a1e59d8716bbd2e73660743fe06acc97ed7d1, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 37bfb464ddca87f203071b5bd562cd91ddc0b40a, >= 2.6.12, >= 2.6.13 < 5.4.296, >= 5.5 < 5.10.240, >= 5.11 < 5.15.187, >= 5.16 < 6.1.143, >= 6.2 < 6.6.96, >= 6.7 < 6.12.36, >= 6.13 < 6.15.4, 2.6.12, 11.0
Fixed versions
5.4.296, 5.10.240, 5.15.187, 6.1.143, 6.6.96, 6.12.36, 6.15.4

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
Not available