Review reviewHigh

CVE-2024-50230

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix kernel bug due to missing clearing of checked flag Syzbot reported that in directory operations after nilfs2 detects filesystem corruption and degrades to read-only, __block_write_begin_int(), which is called to prepare block writes, may fail the BUG_ON check for accesses exceeding the folio/page size, triggering a kernel bug. This was found to be because the "checked" flag of a page/folio was not cleared when it was discarded by nilfs2's own routine, which causes the sanity check of directory entries to be skip...

CVSS
7.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2024.11.09
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix kernel bug due to missing clearing of checked flag Syzbot reported that in directory operations after nilfs2 detects filesystem corruption and degrades to read-only, __block_write_begin_int(), which is called to prepare block writes, may fail the BUG_ON check for accesses exceeding the folio/page size, triggering a kernel bug. This was found to be because the "checked" flag of a page/folio was not cleared when it was discarded by nilfs2's own routine, which causes the sanity check of directory entries to be skip...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 8c26c4e2694a163d525976e804d81cd955bbb40c < 994b2fa13a6c9cf3feca93090a9c337d48e3d60d, >= 8c26c4e2694a163d525976e804d81cd955bbb40c < 64afad73e4623308d8943645e5631f2c7a2d7971, >= 8c26c4e2694a163d525976e804d81cd955bbb40c < aa0cee46c5d3fd9a39575a4c8a4f65f25f095b89, >= 8c26c4e2694a163d525976e804d81cd955bbb40c < f05dbebb8ee34882505d53d83af7d18f28a49248, >= 8c26c4e2694a163d525976e804d81cd955bbb40c < cd0cdb51b15203fa27d4b714be83b7dfffa0b752, >= 8c26c4e2694a163d525976e804d81cd955bbb40c < f2f1fa446676c21edb777e6d2bc4fa8f956fab68, >= 8c26c4e2694a163d525976e804d81cd955bbb40c < 56c6171932a7fb267ac6cb4ff8759b93ee1d0e2e, >= 8c26c4e2694a163d525976e804d81cd955bbb40c < 41e192ad2779cae0102879612dfe46726e4396aa, >= 3.10, >= 3.10 < 4.19.323, >= 4.20 < 5.4.285, >= 5.5 < 5.10.229, >= 5.11 < 5.15.171, >= 5.16 < 6.1.116, >= 6.2 < 6.6.60, >= 6.7 < 6.11.7, 6.12
Fixed versions
4.19.323, 5.4.285, 5.10.229, 5.15.171, 6.1.116, 6.6.60, 6.11.7

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel 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-787