Kernel crash via oversized Squashfs symlink size
Published Sep 18, 2024 · Updated May 12, 2026
Use of uninitialized memory in Linux Squashfs allows local users to crash the kernel by accessing a symbolic link in a malformed filesystem image. squashfs_symlink_read_folio stores the oversized inode size in a signed integer, producing a negative length that skips page initialization. Exploitation requires local access and crafted Squashfs content; the published impact is a kernel crash without confidentiality or integrity loss.
Summary
What happened
Use of uninitialized memory in Linux Squashfs allows local users to crash the kernel by accessing a symbolic link in a malformed filesystem image. squashfs_symlink_read_folio stores the oversized inode size in a signed integer, producing a negative length that skips page initialization. Exploitation requires local access and crafted Squashfs content; the published impact is a kernel crash without confidentiality or integrity loss.
The record
- CVE
- CVE-2024-46744
- Published
- Sep 18, 2024
- Updated
- May 12, 2026
- Vendor
- Siemens
- Product
- SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
- Classifications
- CWE-908
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 18, 2024CVE publishedPublication date reported by the CVE source.
- May 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <V3.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo