Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-49707: ext4: add reserved GDT blocks check

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.28% (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 0dc2fca8e4f9ac4a40e8424a10163369cca0cc06, 33b1bba31f4c784d33d2c2517964bdccdc9204cd, 7c921328ac760bba780bdace41f4cd045f7f1405.

Low priority for now. Upgrade to Linux Linux 0dc2fca8e4f9ac4a40e8424a10163369cca0cc06, 33b1bba31f4c784d33d2c2517964bdccdc9204cd, 7c921328ac760bba780bdace41f4cd045f7f1405 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: add reserved GDT blocks check We capture a NULL pointer issue when resizing a corrupt ext4 image which is freshly clear resize_inode feature (not run e2fsck). It could be simply reproduced by following steps. The problem is because of the resize_inode feature was cleared, and it will convert the filesystem to meta_bg mode in ext4_resize_fs(), but the es->s_reserved_gdt_blocks was not reduced to zero, so could we mistakenly call reserve_backup_gdb() and passing an uninitialized resize_inode to it when adding new group descriptors. mkfs.ext4 /dev/sda 3G tune2fs -O ^resize_inode /dev/sda #forget to run requested e2fsck mount /dev/sda /mnt resize2fs /dev/sda 8G ======== BUG: kernel NULL pointer dereference, address: 0000000000000028 CPU: 19 PID: 3243 Comm: resize2fs Not tainted 5.18.0-rc7-00001-gfde086c5ebfd #748 ... RIP: 0010:ext4_flex_group_add+0xe08/0x2570 ... Call Trace: <TASK> ext4_resize_fs+0xbec/0x1660 __ext4_ioctl+0x1749/0x24e0 ext4_ioctl+0x12/0x20 __x64_sys_ioctl+0xa6/0x110 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f2dd739617b ======== The fix is simple, add a check in ext4_resize_begin() to make sure that the es->s_reserved_gdt_blocks is zero when the resize_inode feature is disabled.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Feb 26, 2025
Updated
Jun 17, 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-49707

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.

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.320
  • linux linux kernel4.10 and later · before 4.14.285
  • linux linux kernel4.15 and later · before 4.19.249
  • linux linux kernel4.20 and later · before 5.4.200
  • linux linux kernel5.5 and later · before 5.10.124
  • linux linux kernel5.11 and later · before 5.15.49
  • linux linux kernel5.16 and later · before 5.18.6
  • linux linux kernel5.19

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.7affected
    • 1c6bd7173d66b3dfdefcedb38cabc1fb03997509 and later · before 0dc2fca8e4f9ac4a40e8424a10163369cca0cc06affected · git
    • 1c6bd7173d66b3dfdefcedb38cabc1fb03997509 and later · before 7c921328ac760bba780bdace41f4cd045f7f1405affected · git
    • 1c6bd7173d66b3dfdefcedb38cabc1fb03997509 and later · before b9747263b13e5290ac4d63bec47e38f701303cadaffected · git
    • 1c6bd7173d66b3dfdefcedb38cabc1fb03997509 and later · before fba54289176702a7caac0b64738406775817f451affected · git
    • 1c6bd7173d66b3dfdefcedb38cabc1fb03997509 and later · before bfd004a1d3a062aac300523d406ac1f3e5f1a82caffected · git
    • 1c6bd7173d66b3dfdefcedb38cabc1fb03997509 and later · before 33b1bba31f4c784d33d2c2517964bdccdc9204cdaffected · git
    • 1c6bd7173d66b3dfdefcedb38cabc1fb03997509 and later · before af75c481a2e45e70f62f5942c93695e95bf7bd21affected · git
    • 1c6bd7173d66b3dfdefcedb38cabc1fb03997509 and later · before b55c3cd102a6f48b90e61c44f7f3dda8c290c694affected · git
    • before 3.7not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.18.14-15.18.14-1

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-49705Feb 26, 2025 · 9p: fix fid refcount leak in v9fs_vfs_atomic_open_dotl
    22Monitor
  • ← EarlierCVE-2022-49706Feb 26, 2025 · zonefs: fix zonefs_iomap_begin() for reads
    28Monitor
  • Later →CVE-2022-49708Feb 26, 2025 · ext4: fix bug_on ext4_mb_use_inode_pa
    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 Linux0dc2fca8e4f9ac4a40e8424a10163369cca0cc06Vendor (CNA)
Linux Linux33b1bba31f4c784d33d2c2517964bdccdc9204cdVendor (CNA)
Linux Linux7c921328ac760bba780bdace41f4cd045f7f1405Vendor (CNA)
Linux Linuxaf75c481a2e45e70f62f5942c93695e95bf7bd21Vendor (CNA)
Linux Linuxb55c3cd102a6f48b90e61c44f7f3dda8c290c694Vendor (CNA)
Linux Linuxb9747263b13e5290ac4d63bec47e38f701303cadVendor (CNA)
Linux Linuxbfd004a1d3a062aac300523d406ac1f3e5f1a82cVendor (CNA)
Linux Linuxfba54289176702a7caac0b64738406775817f451Vendor (CNA)
debian:linux5.18.14-1 · Debian:12Package 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.

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

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

All records