CVE-2022-50286
ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline
- Published
- Updated
- Reserved
- Assigned by
- Linux
Description
In the Linux kernel, the following vulnerability has been resolved: ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline When converting files with inline data to extents, delayed allocations made on a file system created with both the bigalloc and inline options can result in invalid extent status cache content, incorrect reserved cluster counts, kernel memory leaks, and potential kernel panics. With bigalloc, the code that determines whether a block must be delayed allocated searches the extent tree to see if that block maps to a previously allocated cluster. If not, the block is delayed allocated, and otherwise, it isn't. However, if the inline option is also used, and if the file containing the block is marked as able to store data inline, there isn't a valid extent tree associated with the file. The current code in ext4_clu_mapped() calls ext4_find_extent() to search the non-existent tree for a previously allocated cluster anyway, which typically finds nothing, as desired. However, a side effect of the search can be to cache invalid content from the non-existent tree (garbage) in the extent status tree, including bogus entries in the pending reservation tree. To fix this, avoid searching the extent tree when allocating blocks for bigalloc + inline files that are being converted from inline to extent mapped.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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.17% · top 94% of all CVEs (6 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected d40e09f701cf7a44e595a558b067b2b4f67fbf87 – < f83391339d8493b9ff24167516aaa5a5e88d8f81
- affected 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6 – < 6f4200ec76a0d31200c308ec5a71c68df5417004
- affected 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6 – < 9404839e0c9db5a517ea83c0ca3388b39d105fdf
- affected 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6 – < d440d6427a5e3a877c1c259b8d2b216ddb65e185
- affected 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6 – < c0c8edbc8abbe8f16d80a1d794d1ba2c12b6f193
- affected 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6 – < 81b915181c630ee1cffa052e52874fe4e1ba91ac
- affected 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6 – < 131294c35ed6f777bd4e79d42af13b5c41bf2775
- affected 4.19.270 – < 4.19.271
- affected 4.20
- unaffected < 4.20
- unaffected 4.19.271 – ≤ 4.19.*
- unaffected 5.4.229 – ≤ 5.4.*
- unaffected 5.10.163 – ≤ 5.10.*
- unaffected 5.15.87 – ≤ 5.15.*
- unaffected 6.0.18 – ≤ 6.0.*
- unaffected 6.1.4 – ≤ 6.1.*
- unaffected 6.2 – ≤ *
References (7)
- https://git.kernel.org/stable/c/f83391339d8493b9ff24167516aaa5a5e88d8f81 (opens in a new tab)
- https://git.kernel.org/stable/c/6f4200ec76a0d31200c308ec5a71c68df5417004 (opens in a new tab)
- https://git.kernel.org/stable/c/9404839e0c9db5a517ea83c0ca3388b39d105fdf (opens in a new tab)
- https://git.kernel.org/stable/c/d440d6427a5e3a877c1c259b8d2b216ddb65e185 (opens in a new tab)
- https://git.kernel.org/stable/c/c0c8edbc8abbe8f16d80a1d794d1ba2c12b6f193 (opens in a new tab)
- https://git.kernel.org/stable/c/81b915181c630ee1cffa052e52874fe4e1ba91ac (opens in a new tab)
- https://git.kernel.org/stable/c/131294c35ed6f777bd4e79d42af13b5c41bf2775 (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)
- 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://trackcve.app/cve/CVE-2022-50286)Record last updated .