LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52933: Squashfs: fix handling and sanity checking of xattr_ids count

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/

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel Squashfs bug affects how malformed extended-attribute metadata is counted and checked. A corrupted Squashfs filesystem can trigger integer overflow and make a bad table size appear valid. Business urgency depends on whether affected systems mount untrusted or corrupted Squashfs images.

Executive priority

Treat as exposure-dependent. Prioritize remediation for systems that handle externally sourced Squashfs images; otherwise track through normal kernel patching. There is no source evidence here of active exploitation.

Technical view

Squashfs stores xattr_ids from filesystem metadata. The vulnerable code used incorrect integer typing, causing overflow differently on 64-bit and 32-bit systems. The computed xattr index table length can become zero, allowing a corrupted superblock table boundary check to pass incorrectly.

Likely exposure

Exposure is mainly Linux systems running affected kernel builds that process Squashfs filesystems. Prioritize systems mounting user-supplied, downloaded, removable, or update-package images. Systems that do not mount Squashfs images have lower practical exposure.

Exploitation context

The source describes a Sysbot corrupted filesystem trigger and kernel fix details. The bundle does not provide CVSS, CWE, exploit impact, public exploit status, or active exploitation evidence. KEV is false, so active exploitation should not be assumed.

Researcher notes

Focus analysis on Squashfs xattr table parsing and xattr_ids handling. The fix changes xattr_ids typing and casts macro calculations to u64. Impact beyond failed sanity checking is not stated in the provided sources.

Mitigation direction

  • Apply Linux stable kernel fixes or equivalent distribution kernel updates.
  • Check vendor or distribution advisories for fixed kernel packages.
  • Restrict mounting of untrusted Squashfs images where operationally possible.
  • Review image ingestion and update workflows that process Squashfs filesystems.

Validation and detection

  • Inventory Linux kernel versions against vendor advisories and referenced stable commits.
  • Identify hosts or services that mount Squashfs images.
  • Confirm whether Squashfs images can be supplied by users or external parties.
  • Verify updated kernels include the Squashfs xattr_ids type and u64 calculation fixes.
Prepared
Confidence
medium
Sources
9

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-52933 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
8Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxff49cace7b8cf00d27665f7536a863d406963d06, a8717b34003f4f7353b23826617ad872f85d85d8, 3654a0ed0bdc6d70502bfc7c9fec9f1e243dfcad, bddcce15cd1fb9675ddd46a76d8fe2d0a571313b, 506220d2ba21791314af569211ffd8870b8208fa, 506220d2ba21791314af569211ffd8870b8208fa, 506220d2ba21791314af569211ffd8870b8208fa, 91d4f4d0d7bcd6abd9f9288ff40f4edc716f3d4b, eca93bf20f70e0f78c8c28720951942f61a49117unaffected
LinuxLinux5.11, 0, 4.14.306, 4.19.273, 5.4.232, 5.10.168, 5.15.93, 6.1.11, 6.2affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.