CVE-2024-26590

erofs: fix inconsistent per-file compression format

MEDIUM
5.5
CVSS Score
Published: February 22, 2024 at 04:13 PM UTC
Updated: June 17, 2026 at 07:17 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%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: erofs: fix inconsistent per-file compression format EROFS can select compression algorithms on a per-file basis, and each per-file compression algorithm needs to be marked in the on-disk superblock for initialization. However, syzkaller can generate inconsistent crafted images that use an unsupported algorithmtype for specific inodes, e.g. use MicroLZMA algorithmtype even it's not set in `sbi->available_compr_algs`. This can lead to an unexpected "BUG: kernel NULL pointer dereference" if the corresponding decompressor isn't built-in. Fix this by checking against `sbi->available_compr_algs` for each m_algorithmformat request. Incorrect !erofs_sb_has_compr_cfgs preset bitmap is now fixed together since it was harmless previously.

Affected

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

5.16 ≤ v < 6.1.805.16 ≤ v < 6.6.145.16 ≤ v < 6.7.25.16 ≤ v < 6.85.16.0 ≤ v < 6.6.146.7.0 ≤ v < 6.7.25.168f89926290c4b3d31748d5089b27952243be0693
Vendor states this is fixed in 118a8cf504d7dfa519562d000f423ee3ca75d2c4 (fixed)
Vendor states this is fixed in 47467e04816cb297905c0f09bc2d11ef865942d9 (fixed)
Vendor states this is fixed in 823ba1d2106019ddf195287ba53057aee33cf724 (fixed)
Vendor states this is fixed in eed24b816e50c6cd18cbee0ff0d7218c8fced199 (fixed)
Vendor states this is fixed in 5.16 (unaffected)
Vendor states this is fixed in 6.1.80 (unaffected)
Vendor states this is fixed in 6.6.14 (unaffected)
Vendor states this is fixed in 6.7.2 (unaffected)
Vendor states this is fixed in 6.8 (unaffected)

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/118a8cf504d7dfa519562d000f423ee3ca75d2c4
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/47467e04816cb297905c0f09bc2d11ef865942d9
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/823ba1d2106019ddf195287ba53057aee33cf724
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/eed24b816e50c6cd18cbee0ff0d7218c8fced199

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

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

Quick Info

StatusMODIFIED
CWE
CWE-476

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