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-49171ext4: don't BUG if someone dirty pages without asking ext4 first

Description

In the Linux kernel, the following vulnerability has been resolved: ext4: don't BUG if someone dirty pages without asking ext4 first [un]pin_user_pages_remote is dirtying pages without properly warning the file system in advance. A related race was noted by Jan Kara in 2018[1]; however, more recently instead of it being a very hard-to-hit race, it could be reliably triggered by process_vm_writev(2) which was discovered by Syzbot[2]. This is technically a bug in mm/gup.c, but arguably ext4 is fragile in that if some other kernel subsystem dirty pages without properly notifying the file system using page_mkwrite(), ext4 will BUG, while other file systems will not BUG (although data will still be lost). So instead of crashing with a BUG, issue a warning (since there may be potential data loss) and just mark the page as clean to avoid unprivileged denial of service attacks until the problem can be properly fixed. More discussion and background can be found in the thread starting at [2]. [1] https://lore.kernel.org/linux-mm/[email protected] [2] https://lore.kernel.org/r/[email protected]

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 21 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-49171, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.28% · top 80% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected a42afc5f56f319107e987aa6adf2f65d93d527c7 – < 5db60e76edf5680ff1f3a7221036fc44b308f146
    • affected a42afc5f56f319107e987aa6adf2f65d93d527c7 – < d666dfaa571465a19f014534a214c255ea33f301
    • affected a42afc5f56f319107e987aa6adf2f65d93d527c7 – < 0d3a6926f7e8be3c897fa46216ce13b119a9f56a
    • affected a42afc5f56f319107e987aa6adf2f65d93d527c7 – < 5a016c053f426a73752c3b41b60b497b58694d48
    • affected a42afc5f56f319107e987aa6adf2f65d93d527c7 – < 330d0e44fc5a47c27df958ecdd4693a3cb1d8b81
    • affected a42afc5f56f319107e987aa6adf2f65d93d527c7 – < a0856764dc1276ad2dc7891288c2e9246bf11a37
    • affected a42afc5f56f319107e987aa6adf2f65d93d527c7 – < 343117559ef41e992e326f7a92da1a8f254dfa8c
    • affected a42afc5f56f319107e987aa6adf2f65d93d527c7 – < 677c9d30e8487bee6c8e3b034070319d98f6e203
    • affected a42afc5f56f319107e987aa6adf2f65d93d527c7 – < cc5095747edfb054ca2068d01af20be3fcc3634f
  • Linux · Linux

    • affected 2.6.37
    • unaffected < 2.6.37
    • unaffected 4.9.311 – ≤ 4.9.*
    • unaffected 4.14.276 – ≤ 4.14.*
    • unaffected 4.19.238 – ≤ 4.19.*
    • unaffected 5.4.189 – ≤ 5.4.*
    • unaffected 5.10.110 – ≤ 5.10.*
    • unaffected 5.15.33 – ≤ 5.15.*
    • unaffected 5.16.19 – ≤ 5.16.*
    • unaffected 5.17.2 – ≤ 5.17.*
    • unaffected 5.18 – ≤ *

References

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .