Skip to content
Noroxi
CVE-2022-50286· NVD / CVE Program· CNA Linux

ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline

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.16% (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 131294c35ed6f777bd4e79d42af13b5c41bf2775, 4.19.271, 6f4200ec76a0d31200c308ec5a71c68df5417004.
  • Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.

Low priority for now. Upgrade to Linux Linux 131294c35ed6f777bd4e79d42af13b5c41bf2775, 4.19.271, 6f4200ec76a0d31200c308ec5a71c68df5417004 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: 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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Sep 15, 2025
Updated
Aug 5, 2026
EPSS
0.1% · 5th percentile
CWE
—

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.1%

CNA vs NVD score

NVD
5.5
CNA · Linux
7.8
2.3 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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-50286

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 5.4.229
  • linux linux kernel5.5 and later · before 5.10.163
  • linux linux kernel5.11 and later · before 5.15.87
  • linux linux kernel5.16 and later · before 6.0.18
  • linux linux kernel6.1 and later · before 6.1.4

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

    • 4.20affected
    • d40e09f701cf7a44e595a558b067b2b4f67fbf87 and later · before f83391339d8493b9ff24167516aaa5a5e88d8f81affected · git
    • 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6 and later · before 6f4200ec76a0d31200c308ec5a71c68df5417004affected · git
    • 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6 and later · before 9404839e0c9db5a517ea83c0ca3388b39d105fdfaffected · git
    • 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6 and later · before d440d6427a5e3a877c1c259b8d2b216ddb65e185affected · git
    • 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6 and later · before c0c8edbc8abbe8f16d80a1d794d1ba2c12b6f193affected · git
    • 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6 and later · before 81b915181c630ee1cffa052e52874fe4e1ba91acaffected · git
    • 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6 and later · before 131294c35ed6f777bd4e79d42af13b5c41bf2775affected · git
    • 4.19.270 and later · before 4.19.271affected · semver
    • before 4.20not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.4-16.1.4-1
Red Hat:enterprise_linux:8::baseosbpftoolbefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseosbpftool-debuginfobefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernelbefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-abi-stablelistsbefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-corebefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debugbefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debug-corebefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debug-debuginfobefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debug-develbefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debug-modulesbefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debug-modules-extrabefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debuginfobefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debuginfo-common-aarch64before 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debuginfo-common-ppc64lebefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debuginfo-common-s390xbefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debuginfo-common-x86_64before 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-develbefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-docbefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-modulesbefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-modules-extrabefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-toolsbefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-tools-debuginfobefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10
Red Hat:enterprise_linux:8::baseoskernel-tools-libsbefore 0:4.18.0-553.el8_100:4.18.0-553.el8_10

+90

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • 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
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2022-50284Sep 15, 2025 · ipc: fix memory leak in init_mqueue_fs()
    22Monitor
  • ← EarlierCVE-2022-50285Sep 15, 2025 · mm,hugetlb: take hugetlb_lock before decrementing h->resv_huge_pages
    22Monitor
  • Later →CVE-2022-50287Sep 15, 2025 · drm/i915/bios: fix a memory leak in generate_lfp_data_ptrs
    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 Linux131294c35ed6f777bd4e79d42af13b5c41bf2775Vendor (CNA)
Linux Linux4.19.271Vendor (CNA)
Linux Linux6f4200ec76a0d31200c308ec5a71c68df5417004Vendor (CNA)
Linux Linux81b915181c630ee1cffa052e52874fe4e1ba91acVendor (CNA)
Linux Linux9404839e0c9db5a517ea83c0ca3388b39d105fdfVendor (CNA)
Linux Linuxc0c8edbc8abbe8f16d80a1d794d1ba2c12b6f193Vendor (CNA)
Linux Linuxd440d6427a5e3a877c1c259b8d2b216ddb65e185Vendor (CNA)
Linux Linuxf83391339d8493b9ff24167516aaa5a5e88d8f81Vendor (CNA)
debian:linux6.1.4-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
rocky linux:kernel0:4.18.0-553.123.1.el8_10.cloud.0.1 · Rocky Linux:8Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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.

No nightly-computed relations.

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)

—

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. Fix✗ → ✓

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

References

Show all references (6 more)

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

All records