CVE-2023-52933

Squashfs: fix handling and sanity checking of xattr_ids count

MEDIUM
5.5
CVSS Score
Published: March 27, 2025 at 04:37 PM UTC
Updated: June 17, 2026 at 06:43 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.3%

Description

In the Linux kernel, the following vulnerability has been resolved: Squashfs: fix handling and sanity checking of xattr_ids count A Sysbot [1] corrupted filesystem exposes two flaws in the handling and sanity checking of the xattr_ids count in the filesystem. Both of these flaws cause computation overflow due to incorrect typing. In the corrupted filesystem the xattr_ids value is 4294967071, which stored in a signed variable becomes the negative number -225. Flaw 1 (64-bit systems only): The signed integer xattr_ids variable causes sign extension. This causes variable overflow in the SQUASHFS_XATTR_*(A) macros. The variable is first multiplied by sizeof(struct squashfs_xattr_id) where the type of the sizeof operator is "unsigned long". On a 64-bit system this is 64-bits in size, and causes the negative number to be sign extended and widened to 64-bits and then become unsigned. This produces the very large number 18446744073709548016 or 2^64 - 3600. This number when rounded up by SQUASHFS_METADATA_SIZE - 1 (8191 bytes) and divided by SQUASHFS_METADATA_SIZE overflows and produces a length of 0 (stored in len). Flaw 2 (32-bit systems only): On a 32-bit system the integer variable is not widened by the unsigned long type of the sizeof operator (32-bits), and the signedness of the variable has no effect due it always being treated as unsigned. The above corrupted xattr_ids value of 4294967071, when multiplied overflows and produces the number 4294963696 or 2^32 - 3400. This number when rounded up by SQUASHFS_METADATA_SIZE - 1 (8191 bytes) and divided by SQUASHFS_METADATA_SIZE overflows again and produces a length of 0. The effect of the 0 length computation: In conjunction with the corrupted xattr_ids field, the filesystem also has a corrupted xattr_table_start value, where it matches the end of filesystem value of 850. This causes the following sanity check code to fail because the incorrectly computed len of 0 matches the incorrect size of the table reported by the superblock (0 bytes). len = SQUASHFS_XATTR_BLOCK_BYTES(*xattr_ids); indexes = SQUASHFS_XATTR_BLOCKS(*xattr_ids); /* * The computed size of the index table (len bytes) should exactly * match the table start and end points */ start = table_start + sizeof(*id_table); end = msblk->bytes_used; if (len != (end - start)) return ERR_PTR(-EINVAL); Changing the xattr_ids variable to be "usigned int" fixes the flaw on a 64-bit system. This relies on the fact the computation is widened by the unsigned long type of the sizeof operator. Casting the variable to u64 in the above macro fixes this flaw on a 32-bit system. It also means 64-bit systems do not implicitly rely on the type of the sizeof operator to widen the computation. [1] https://lore.kernel.org/lkml/[email protected]/

Affected

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

v ≥ 4.4.258v ≥ 4.9.2584.14.222 ≤ v < 4.14.3064.19.176 ≤ v < 4.19.2734.4.258 ≤ v < 4.54.9.258 ≤ v < 4.105.10.16 ≤ v < 5.10.1685.11 ≤ v < 5.15.935.11 ≤ v < 6.1.115.11 ≤ v < 6.25.11.1 ≤ v < 5.15.935.16 ≤ v < 6.1.115.4.98 ≤ v < 5.4.2323654a0ed0bdc6d70502bfc7c9fec9f1e243dfcad4.14.2224.19.1764.4.2584.9.2585.10.165.115.4.98506220d2ba21791314af569211ffd8870b8208fa6.2 rc16.2 rc26.2 rc36.2 rc46.2 rc56.2 rc691d4f4d0d7bcd6abd9f9288ff40f4edc716f3d4ba8717b34003f4f7353b23826617ad872f85d85d8bddcce15cd1fb9675ddd46a76d8fe2d0a571313beca93bf20f70e0f78c8c28720951942f61a49117ff49cace7b8cf00d27665f7536a863d406963d06
Vendor states this is fixed in 1369322c1de52c7b9b988b95c9903110a4566778 (fixed)
Vendor states this is fixed in 5c4d4a83bf1a862d80c1efff1c6e3ce33b501e2e (fixed)
Vendor states this is fixed in 7fe583c9bec10cd4b76231c51b37f3e4ca646e01 (fixed)
Vendor states this is fixed in 997bed0f3cde78a3e639d624985bf4a95cf767e6 (fixed)
Vendor states this is fixed in a7da7d01ac5ce9b369a1ac70e1197999cc6c9686 (fixed)
Vendor states this is fixed in b38c3e9e0adc01956cc3e5a52e4d3f92f79d88e2 (fixed)
Vendor states this is fixed in f65c4bbbd682b0877b669828b4e033b8d5d0a2dc (fixed)
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.14.306 (unaffected)
Vendor states this is fixed in 4.19.273 (unaffected)
Affected range stops below 4.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.168 (unaffected)
Vendor states this is fixed in 5.11 (unaffected)
Vendor states this is fixed in 5.15.93 (unaffected)
Vendor states this is fixed in 5.4.232 (unaffected)
Vendor states this is fixed in 6.1.11 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)

References (7)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/1369322c1de52c7b9b988b95c9903110a4566778
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/5c4d4a83bf1a862d80c1efff1c6e3ce33b501e2e
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/7fe583c9bec10cd4b76231c51b37f3e4ca646e01
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/997bed0f3cde78a3e639d624985bf4a95cf767e6
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/a7da7d01ac5ce9b369a1ac70e1197999cc6c9686
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/b38c3e9e0adc01956cc3e5a52e4d3f92f79d88e2
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/f65c4bbbd682b0877b669828b4e033b8d5d0a2dc

CVSS

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

Quick Info

StatusANALYZED
CWE
CWE-190

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