Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2022-50286ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 11 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

CVSS scores of CVE-2022-50286, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium5.5CVSS: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 (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • 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
  • Linux · Linux

    • 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

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-50286 badge
[![CVE-2022-50286](https://cveledger.app/badge/CVE-2022-50286.svg)](https://cveledger.app/cve/CVE-2022-50286)

Record last updated .