Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-52622: ext4: avoid online resizing failures due to oversized flex bg

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.24% (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 5d1935ac02ca5aee364a449a35e2977ea84509b0, 6d2cbf517dcabc093159cf138ad5712c9c7fa954, 8b1413dbfe49646eda2c00c0f1144ee9d3368e0c.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 5d1935ac02ca5aee364a449a35e2977ea84509b0, 6d2cbf517dcabc093159cf138ad5712c9c7fa954, 8b1413dbfe49646eda2c00c0f1144ee9d3368e0c 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: avoid online resizing failures due to oversized flex bg When we online resize an ext4 filesystem with a oversized flexbg_size, mkfs.ext4 -F -G 67108864 $dev -b 4096 100M mount $dev $dir resize2fs $dev 16G the following WARN_ON is triggered: ================================================================== WARNING: CPU: 0 PID: 427 at mm/page_alloc.c:4402 __alloc_pages+0x411/0x550 Modules linked in: sg(E) CPU: 0 PID: 427 Comm: resize2fs Tainted: G E 6.6.0-rc5+ #314 RIP: 0010:__alloc_pages+0x411/0x550 Call Trace: <TASK> __kmalloc_large_node+0xa2/0x200 __kmalloc+0x16e/0x290 ext4_resize_fs+0x481/0xd80 __ext4_ioctl+0x1616/0x1d90 ext4_ioctl+0x12/0x20 __x64_sys_ioctl+0xf0/0x150 do_syscall_64+0x3b/0x90 ================================================================== This is because flexbg_size is too large and the size of the new_group_data array to be allocated exceeds MAX_ORDER. Currently, the minimum value of MAX_ORDER is 8, the minimum value of PAGE_SIZE is 4096, the corresponding maximum number of groups that can be allocated is: (PAGE_SIZE << MAX_ORDER) / sizeof(struct ext4_new_group_data) ≈ 21845 And the value that is down-aligned to the power of 2 is 16384. Therefore, this value is defined as MAX_RESIZE_BG, and the number of groups added each time does not exceed this value during resizing, and is added multiple times to complete the online resizing. The difference is that the metadata in a flex_bg may be more dispersed.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Mar 26, 2024
Updated
Oct 15, 2026
EPSS
0.2% · 15th 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-2023-52622

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
debiandebian linux

Affected versions

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

  • debian debian linux10.0
  • linux linux kernel4.20 and later · before 5.4.269
  • linux linux kernel5.5 and later · before 5.10.210
  • linux linux kernel5.11 and later · before 5.15.149
  • linux linux kernelbefore 4.19.307
  • linux linux kernel6.2 and later · before 6.6.16
  • linux linux kernel6.7 and later · before 6.7.4
  • linux linux kernel5.16 and later · before 6.1.77

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

    • 3.3affected
    • 28c7bac0091687e6116ebd6c179e154ae4053c90 and later · before cd1f93ca97a9136989f3bd2bf90696732a2ed644affected · git
    • 28c7bac0091687e6116ebd6c179e154ae4053c90 and later · before b183fe8702e78bba3dcef8e7193cab6898abee07affected · git
    • 28c7bac0091687e6116ebd6c179e154ae4053c90 and later · before cfbbb3199e71b63fc26cee0ebff327c47128a1e8affected · git
    • 28c7bac0091687e6116ebd6c179e154ae4053c90 and later · before d76c8d7ffe163c6bf2f1ef680b0539c2b3902b90affected · git
    • 28c7bac0091687e6116ebd6c179e154ae4053c90 and later · before 6d2cbf517dcabc093159cf138ad5712c9c7fa954affected · git
    • 28c7bac0091687e6116ebd6c179e154ae4053c90 and later · before 8b1413dbfe49646eda2c00c0f1144ee9d3368e0caffected · git
    • 28c7bac0091687e6116ebd6c179e154ae4053c90 and later · before dc3e0f55bec4410f3d74352c4a7c79f518088ee2affected · git
    • 28c7bac0091687e6116ebd6c179e154ae4053c90 and later · before 5d1935ac02ca5aee364a449a35e2977ea84509b0affected · git
    • before 3.3not 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.82-16.1.82-1
Debian:13linuxbefore 6.7.7-16.7.7-1
openSUSE:Leap 15.6dtb-aarch64before 6.4.0-150600.23.14.16.4.0-150600.23.14.1
openSUSE:Leap 15.6kernel-64kbbefore 6.4.0-150600.23.14.16.4.0-150600.23.14.1
openSUSE:Leap 15.6kernel-azurebefore 6.4.0-150600.8.8.26.4.0-150600.8.8.2
openSUSE:Leap 15.6kernel-debugbefore 6.4.0-150600.23.14.26.4.0-150600.23.14.2
openSUSE:Leap 15.6kernel-defaultbefore 6.4.0-150600.23.14.26.4.0-150600.23.14.2
openSUSE:Leap 15.6kernel-default-basebefore 6.4.0-150600.23.14.2.150600.12.4.36.4.0-150600.23.14.2.150600.12.4.3
openSUSE:Leap 15.6kernel-docsbefore 6.4.0-150600.23.14.26.4.0-150600.23.14.2
openSUSE:Leap 15.6kernel-kvmsmallbefore 6.4.0-150600.23.14.26.4.0-150600.23.14.2
openSUSE:Leap 15.6kernel-obs-buildbefore 6.4.0-150600.23.14.26.4.0-150600.23.14.2
openSUSE:Leap 15.6kernel-obs-qabefore 6.4.0-150600.23.14.26.4.0-150600.23.14.2
openSUSE:Leap 15.6kernel-rtbefore 6.4.0-150600.10.5.16.4.0-150600.10.5.1
openSUSE:Leap 15.6kernel-rt_debugbefore 6.4.0-150600.10.5.16.4.0-150600.10.5.1
openSUSE:Leap 15.6kernel-sourcebefore 6.4.0-150600.23.14.26.4.0-150600.23.14.2
openSUSE:Leap 15.6kernel-source-azurebefore 6.4.0-150600.8.8.26.4.0-150600.8.8.2
openSUSE:Leap 15.6kernel-source-rtbefore 6.4.0-150600.10.5.16.4.0-150600.10.5.1
openSUSE:Leap 15.6kernel-symsbefore 6.4.0-150600.23.14.26.4.0-150600.23.14.2
openSUSE:Leap 15.6kernel-syms-azurebefore 6.4.0-150600.8.8.16.4.0-150600.8.8.1
openSUSE:Leap 15.6kernel-syms-rtbefore 6.4.0-150600.10.5.16.4.0-150600.10.5.1
openSUSE:Leap 15.6kernel-zfcpdumpbefore 6.4.0-150600.23.14.26.4.0-150600.23.14.2
Red Hat:rhel_eus:9.4::appstreambpftool-debuginfobefore 0:7.3.0-427.70.1.el9_40:7.3.0-427.70.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-427.70.1.el9_40:5.14.0-427.70.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-develbefore 0:5.14.0-427.70.1.el9_40:5.14.0-427.70.1.el9_4

+96

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-2024-26649Mar 26, 2024 · drm/amdgpu: Fix the null pointer when load rlc firmware
    22Monitor
  • ← EarlierCVE-2024-26645Mar 26, 2024 · tracing: Ensure visibility when inserting an element into tracing_map
    22Monitor
  • Later →CVE-2024-26652Mar 27, 2024 · net: pds_core: Fix possible double free in error handling path
    16Monitor

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 Linux5d1935ac02ca5aee364a449a35e2977ea84509b0Vendor (CNA)
Linux Linux6d2cbf517dcabc093159cf138ad5712c9c7fa954Vendor (CNA)
Linux Linux8b1413dbfe49646eda2c00c0f1144ee9d3368e0cVendor (CNA)
Linux Linuxb183fe8702e78bba3dcef8e7193cab6898abee07Vendor (CNA)
Linux Linuxcd1f93ca97a9136989f3bd2bf90696732a2ed644Vendor (CNA)
Linux Linuxcfbbb3199e71b63fc26cee0ebff327c47128a1e8Vendor (CNA)
Linux Linuxd76c8d7ffe163c6bf2f1ef680b0539c2b3902b90Vendor (CNA)
Linux Linuxdc3e0f55bec4410f3d74352c4a7c79f518088ee2Vendor (CNA)
almalinux:bpftool4.18.0-553.16.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.16.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.16.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.16.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.16.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.16.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.16.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.16.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.16.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.16.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.16.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.16.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.82-1 · Debian:12Package registry (OSV)
opensuse:dtb-aarch646.4.0-150600.23.14.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-64kb6.4.0-150600.23.14.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-debug6.4.0-150600.23.14.2 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default6.4.0-150600.23.14.2 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default-base6.4.0-150600.23.14.2.150600.12.4.3 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-docs6.4.0-150600.23.14.2 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-kvmsmall6.4.0-150600.23.14.2 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-obs-build6.4.0-150600.23.14.2 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-obs-qa6.4.0-150600.23.14.2 · openSUSE:Leap 15.6Package registry (OSV)

+27

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-2021-471371 days apartnet: lantiq: fix memory corruption in RX ring
    39Monitor
  • CVE-2024-3596955 days apartipv6: fix race condition between ipv6_get_ifaddr and ipv6_del_addr
    35Monitor
  • CVE-2021-4755159 days apartdrm/amd/amdkfd: Fix kernel panic when reset failed and been triggered again
    31Monitor
  • CVE-2024-3402790 days apartf2fs: compress: fix to cover {reserve,release}_compress_blocks() w/ cp_rwsem lock
    31Monitor
  • CVE-2021-4713011 days apartnvmet: fix freeing unallocated p2pmem
    30Monitor
  • CVE-2024-2689422 days apartACPI: processor_idle: Fix memory leak in acpi_processor_power_exit()
    24Monitor

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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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-770 · Allocation of Resources Without Limits or Throttling

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.

Change log

  1. Fix✗ → ✓

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

References

Show all references (11 more)

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

All records