CVE-2024-47669nilfs2: fix state management in error path of log writing function
- 7.3HighCVSS base score
- 0.22%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix state management in error path of log writing function After commit a694291a6211 ("nilfs2: separate wait function from nilfs_segctor_write") was applied, the log writing function nilfs_segctor_do_construct() was able to issue I/O requests continuously even if user data blocks were split into multiple logs across segments, but two potential flaws were introduced in its error handling. First, if nilfs_segctor_begin_construction() fails while creating the second or subsequent logs, the log writing function returns without calling nilfs_segctor_abort_construction(), so the writeback flag set on pages/folios will remain uncleared. This causes page cache operations to hang waiting for the writeback flag. For example, truncate_inode_pages_final(), which is called via nilfs_evict_inode() when an inode is evicted from memory, will hang. Second, the NILFS_I_COLLECTED flag set on normal inodes remain uncleared. As a result, if the next log write involves checkpoint creation, that's fine, but if a partial log write is performed that does not, inodes with NILFS_I_COLLECTED set are erroneously removed from the "sc_dirty_files" list, and their data and b-tree blocks may not be written to the device, corrupting the block mapping. Fix these issues by uniformly calling nilfs_segctor_abort_construction() on failure of each step in the loop in nilfs_segctor_do_construct(), having it clean up logs and segment usages according to progress, and correcting the conditions for calling nilfs_redirty_inodes() to ensure that the NILFS_I_COLLECTED flag is cleared.
Timeline
ID reserved
By Linux
- 9 days later
· 9 days later
Published
- 22 months later
· 22 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H |
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.22% · top 88% of all CVEs (15 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.3.
Affected products
- affected a694291a6211537189c6080f77f63cdabfc9b63e – < 40a2757de2c376ef8a08d9ee9c81e77f3c750adf
- affected a694291a6211537189c6080f77f63cdabfc9b63e – < 036441e8438b29111fa75008f0ce305fb4e83c0a
- affected a694291a6211537189c6080f77f63cdabfc9b63e – < efdde00d4a1ef10bb71e09ebc67823a3d3ad725b
- affected a694291a6211537189c6080f77f63cdabfc9b63e – < 3e349d7191f0688fc9808ef24fd4e4b4ef5ca876
- affected a694291a6211537189c6080f77f63cdabfc9b63e – < 30562eff4a6dd35c4b5be9699ef61ad9f5f20a06
- affected a694291a6211537189c6080f77f63cdabfc9b63e – < 0a1a961bde4351dc047ffdeb2f1311ca16a700cc
- affected a694291a6211537189c6080f77f63cdabfc9b63e – < 74866c16ea2183f52925fa5d76061a1fe7f7737b
- affected a694291a6211537189c6080f77f63cdabfc9b63e – < 6576dd6695f2afca3f4954029ac4a64f82ba60ab
- affected 2.6.33
- unaffected < 2.6.33
- unaffected 4.19.322 – ≤ 4.19.*
- unaffected 5.4.284 – ≤ 5.4.*
- unaffected 5.10.226 – ≤ 5.10.*
- unaffected 5.15.167 – ≤ 5.15.*
- unaffected 6.1.110 – ≤ 6.1.*
- unaffected 6.6.51 – ≤ 6.6.*
- unaffected 6.10.10 – ≤ 6.10.*
- unaffected 6.11 – ≤ *
References
References9
- https://git.kernel.org/stable/c/40a2757de2c376ef8a08d9ee9c81e77f3c750adf (opens in a new tab)
- https://git.kernel.org/stable/c/036441e8438b29111fa75008f0ce305fb4e83c0a (opens in a new tab)
- https://git.kernel.org/stable/c/efdde00d4a1ef10bb71e09ebc67823a3d3ad725b (opens in a new tab)
- https://git.kernel.org/stable/c/3e349d7191f0688fc9808ef24fd4e4b4ef5ca876 (opens in a new tab)
- https://git.kernel.org/stable/c/30562eff4a6dd35c4b5be9699ef61ad9f5f20a06 (opens in a new tab)
- https://git.kernel.org/stable/c/0a1a961bde4351dc047ffdeb2f1311ca16a700cc (opens in a new tab)
- https://git.kernel.org/stable/c/74866c16ea2183f52925fa5d76061a1fe7f7737b (opens in a new tab)
- https://git.kernel.org/stable/c/6576dd6695f2afca3f4954029ac4a64f82ba60ab (opens in a new tab)
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-42590 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-47669)Record last updated .