Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-49171: ext4: don't BUG if someone dirty pages without asking ext4 first

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.27% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0d3a6926f7e8be3c897fa46216ce13b119a9f56a, 330d0e44fc5a47c27df958ecdd4693a3cb1d8b81, 343117559ef41e992e326f7a92da1a8f254dfa8c.

Low priority for now. Upgrade to Linux Linux 0d3a6926f7e8be3c897fa46216ce13b119a9f56a, 330d0e44fc5a47c27df958ecdd4693a3cb1d8b81, 343117559ef41e992e326f7a92da1a8f254dfa8c or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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/20180103100430.GE4911@quack2.suse.cz [2] https://lore.kernel.org/r/Yg0m6IjcNmfaSokM@google.com

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Feb 26, 2025
Updated
Nov 5, 2026
EPSS
0.2% · 20th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-49171

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernelbefore 4.9.311
  • linux linux kernel4.10 and later · before 4.14.276
  • linux linux kernel4.15 and later · before 4.19.238
  • linux linux kernel4.20 and later · before 5.4.189
  • linux linux kernel5.5 and later · before 5.10.110
  • linux linux kernel5.11 and later · before 5.15.33
  • linux linux kernel5.16 and later · before 5.16.19
  • linux linux kernel5.17 and later · before 5.17.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.37affected
    • a42afc5f56f319107e987aa6adf2f65d93d527c7 and later · before 5db60e76edf5680ff1f3a7221036fc44b308f146affected · git
    • a42afc5f56f319107e987aa6adf2f65d93d527c7 and later · before d666dfaa571465a19f014534a214c255ea33f301affected · git
    • a42afc5f56f319107e987aa6adf2f65d93d527c7 and later · before 0d3a6926f7e8be3c897fa46216ce13b119a9f56aaffected · git
    • a42afc5f56f319107e987aa6adf2f65d93d527c7 and later · before 5a016c053f426a73752c3b41b60b497b58694d48affected · git
    • a42afc5f56f319107e987aa6adf2f65d93d527c7 and later · before 330d0e44fc5a47c27df958ecdd4693a3cb1d8b81affected · git
    • a42afc5f56f319107e987aa6adf2f65d93d527c7 and later · before a0856764dc1276ad2dc7891288c2e9246bf11a37affected · git
    • a42afc5f56f319107e987aa6adf2f65d93d527c7 and later · before 343117559ef41e992e326f7a92da1a8f254dfa8caffected · git
    • a42afc5f56f319107e987aa6adf2f65d93d527c7 and later · before 677c9d30e8487bee6c8e3b034070319d98f6e203affected · git
    • a42afc5f56f319107e987aa6adf2f65d93d527c7 and later · before cc5095747edfb054ca2068d01af20be3fcc3634faffected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.17.3-15.17.3-1
SUSE:Linux Enterprise Live Patching 12 SP5kernel-defaultbefore 4.12.14-122.258.14.12.14-122.258.1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_68before 1-8.3.11-8.3.1
SUSE:Linux Enterprise Server 12 SP5-LTSSkernel-sourcebefore 4.12.14-122.258.14.12.14-122.258.1
SUSE:Linux Enterprise Server 12 SP5-LTSSkernel-symsbefore 4.12.14-122.258.14.12.14-122.258.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2022-49157Feb 26, 2025 · scsi: qla2xxx: Fix premature hw access after PCI error
    22Monitor
  • ← EarlierCVE-2022-49159Feb 26, 2025 · scsi: qla2xxx: Implement ref count for SRB
    22Monitor
  • Later →CVE-2022-49174Feb 26, 2025 · ext4: fix ext4_mb_mark_bb() with flex_bg with fast_commit
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0d3a6926f7e8be3c897fa46216ce13b119a9f56aVendor (CNA)
Linux Linux330d0e44fc5a47c27df958ecdd4693a3cb1d8b81Vendor (CNA)
Linux Linux343117559ef41e992e326f7a92da1a8f254dfa8cVendor (CNA)
Linux Linux5a016c053f426a73752c3b41b60b497b58694d48Vendor (CNA)
Linux Linux5db60e76edf5680ff1f3a7221036fc44b308f146Vendor (CNA)
Linux Linux677c9d30e8487bee6c8e3b034070319d98f6e203Vendor (CNA)
Linux Linuxa0856764dc1276ad2dc7891288c2e9246bf11a37Vendor (CNA)
Linux Linuxcc5095747edfb054ca2068d01af20be3fcc3634fVendor (CNA)
Linux Linuxd666dfaa571465a19f014534a214c255ea33f301Vendor (CNA)
debian:linux5.17.3-1 · Debian:12Package registry (OSV)
suse:kernel-default4.12.14-122.258.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package registry (OSV)
suse:kernel-source4.12.14-122.258.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:kernel-syms4.12.14-122.258.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_681-8.3.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-31739429 days apartcrypto: tegra - Add missing CRYPTO_ALG_ASYNC
    35Monitor
  • CVE-2026-52952483 days apartiommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset
    35Monitor
  • CVE-2025-39803201 days apartscsi: ufs: core: Remove WARN_ON_ONCE() call from ufshcd_uic_cmd_compl()
    31Monitor
  • CVE-2023-52621337 days apartbpf: Check rcu_read_lock_trace_held() before calling bpf map helpers
    31Monitor
  • CVE-2026-31398401 days apartmm/rmap: fix incorrect pte restoration for lazyfree folios
    31Monitor
  • CVE-2026-46117456 days apartRDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss()
    31Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-617 · Reachable Assertion

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records