CVE-2022-49739

gfs2: Always check inode size of inline inodes

MEDIUM
5.5
CVSS Score
Published: March 27, 2025 at 04:42 PM UTC
Updated: August 5, 2026 at 09:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: gfs2: Always check inode size of inline inodes Check if the inode size of stuffed (inline) inodes is within the allowed range when reading inodes from disk (gfs2_dinode_in()). This prevents us from on-disk corruption. The two checks in stuffed_readpage() and gfs2_unstuffer_page() that just truncate inline data to the maximum allowed size don't actually make sense, and they can be removed now as well.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 4.19.2802.6.19 ≤ v < 4.19.2802.6.19 ≤ v < 5.10.1772.6.19 ≤ v < 5.15.932.6.19 ≤ v < 5.4.2402.6.19 ≤ v < 6.1.112.6.19 ≤ v < 6.24.20 ≤ v < 5.4.2405.11 ≤ v < 5.15.935.16 ≤ v < 6.1.115.5 ≤ v < 5.10.1772.6.19b3b94faa5fe5968827ba0640ee9fba4b3e7f736e
Vendor states this is fixed in 45df749f827c286adbc951f2a4865b67f0442ba9 (fixed)
Vendor states this is fixed in 46c9088cabd4d0469fdb61ac2a9c5003057fe94d (fixed)
Vendor states this is fixed in 4d4cb76636134bf9a0c9c3432dae936f99954586 (fixed)
Vendor states this is fixed in 70376c7ff31221f1d21db5611d8209e677781d3a (fixed)
Vendor states this is fixed in 7c414f6f06e9a3934901b6edc3177ae5a1e07094 (fixed)
Vendor states this is fixed in d458a0984429c2d47e60254f5bc4119cbafe83a2 (fixed)
Vendor states this is fixed in 2.6.19 (unaffected)
Vendor states this is fixed in 4.19.280 (unaffected)
Vendor states this is fixed in 5.10.177 (unaffected)
Vendor states this is fixed in 5.15.93 (unaffected)
Vendor states this is fixed in 5.4.240 (unaffected)
Vendor states this is fixed in 6.1.11 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)

References (6)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/45df749f827c286adbc951f2a4865b67f0442ba9
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/46c9088cabd4d0469fdb61ac2a9c5003057fe94d
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/4d4cb76636134bf9a0c9c3432dae936f99954586
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/70376c7ff31221f1d21db5611d8209e677781d3a
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/7c414f6f06e9a3934901b6edc3177ae5a1e07094
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/d458a0984429c2d47e60254f5bc4119cbafe83a2

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card