VDB

CVE-2023-52933

CVE-2023-52933 PUBLISHED

Squashfs: fix handling and sanity checking of xattr_ids count

Reported by linux · Published March 27, 2025

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/000000000000cd44f005f1a0f17f@google.com/

EPSS 0.27% · 19.1th percentile

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
perfAmazon Linux4.14.309-231.529.amzn2
kernel-libbpf-develAmazon Linux6.1.12-17.42.amzn2023
kernelAmazon Linux4.14.309-231.529.amzn2
LinuxLinuxf65c4bbbd682b0877b669828b4e033b8d5d0a2dc, b38c3e9e0adc01956cc3e5a52e4d3f92f79d88e2, a7da7d01ac5ce9b369a1ac70e1197999cc6c9686, 997bed0f3cde78a3e639d624985bf4a95cf767e6, 7fe583c9bec10cd4b76231c51b37f3e4ca646e01, 5c4d4a83bf1a862d80c1efff1c6e3ce33b501e2e, 5.11, 4.14.306, 1369322c1de52c7b9b988b95c9903110a4566778

Risk scores

EPSS Score
0.27%
19.1th percentile

Affected products

VendorProductVersions
LinuxLinuxff49cace7b8cf00d27665f7536a863d406963d06, a8717b34003f4f7353b23826617ad872f85d85d8, 3654a0ed0bdc6d70502bfc7c9fec9f1e243dfcad
LinuxLinux5.11, 0, 4.14.306
amazon:2perf0
amazon:2023kernel-libbpf-devel0
amazon:2kernel0
LinuxLinux4.19.273, 4.9.258, 5.10.168
amazon:2023python3-perf0
amazon:2023kernel-devel0
amazon:2023kernel-headers0
amazon:2kernel-tools0
amazon:2023kernel-libbpf0
amazon:2023kernel-livepatch-6.1.12-17.420
amazon:2023bpftool0
amazon:2023kernel-tools-devel0
amazon:2023perf0
amazon:2kernel-tools-devel0
amazon:2kernel-livepatch-4.14.309-231.5290
amazon:2023kernel-tools0
linuxlinux_kernel5.4.98, 4.9.258, 4.4.258
amazon:2023kernel0

…and 4 more

Timeline

  • Mar 27, 2025 CVE Published
  • Mar 28, 2025 EPSS Score (30 in total, the first dated here)
  • Mar 28, 2025 Coalition ESS Score (10 in total, the first dated here)
  • Dec 5, 2025 CVE Updated
  • Jan 25, 2026 Security Advisory (156 in total, the first dated here)
  • Sep 5, 2026 Distribution Patch (148 in total, the first dated here)

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2023-52933
vulnetix vdb fixes CVE-2023-52933

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2023-52933/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›