CVE-2022-33967

Exp

squashfs filesystem implementation of U-Boot versions from v2020.10-rc2 to v2022.07-rc5 contains a heap-based buffer overflow vulnerability due to a defect in the metadata reading process. Loading a specially crafted squashfs image may lead to a denial-of-service (DoS) condition or arbitrary code execution.

Published: 2022-07-20 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-33967 is rated Exploit Available (59.3/100): CVSS High severity, with low exploitation likelihood (EPSS 0.51%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2022-33967

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2022-33967

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 1.04% 0.51% -0.53%
2 2026-06-09 0.56% 1.04% +0.48%
3 2026-05-06 — 0.56% —

Full EPSS history (25 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-33967

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]

Weakness enumeration for CVE-2022-33967

OS Trackers for CVE-2022-33967

vendor priority summary link
alpine — CVE-2022-33967: 1 source package rows (u-boot); 8 state rows across 5 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 0, open 8. https://security.alpinelinux.org/vuln/CVE-2022-33967
debian not yet assigned CVE-2022-33967 not yet assigned priority: Debian including 1 source packages (u-boot), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-33967
suse medium CVE-2022-33967 severity moderate: SUSE including 174 source package names (u-boot, u-boot-avnetultra96rev1-2021.01-150300.7.15.1, …), 309 product×package rows across 36 product lines (SUSE CaaS Platform 4.0, SUSE Enterprise Storage 6, … (36 product lines)): Fixed 263, Known Not Affected 46. https://www.suse.com/security/cve/CVE-2022-33967/
ubuntu medium CVE-2022-33967 medium priority: Ubuntu including 1 source packages (u-boot), 14 status rows across 14 suites (bionic, focal, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 7, released 3, ignored 2, needs-triage 2. https://ubuntu.com/security/CVE-2022-33967

Affected software / configurations for CVE-2022-33967

Vendor Product Version Raw CPE
denx u-boot 2020.10 cpe:2.3:a:denx:u-boot:2020.10:rc2:*:*:*:*:*:*
denx u-boot 2020.10 cpe:2.3:a:denx:u-boot:2020.10:rc3:*:*:*:*:*:*
denx u-boot 2020.10 cpe:2.3:a:denx:u-boot:2020.10:rc4:*:*:*:*:*:*
denx u-boot 2020.10 cpe:2.3:a:denx:u-boot:2020.10:rc5:*:*:*:*:*:*
denx u-boot 2021.01 cpe:2.3:a:denx:u-boot:2021.01:-:*:*:*:*:*:*
denx u-boot 2021.01 cpe:2.3:a:denx:u-boot:2021.01:rc1:*:*:*:*:*:*
denx u-boot 2021.01 cpe:2.3:a:denx:u-boot:2021.01:rc2:*:*:*:*:*:*
denx u-boot 2021.01 cpe:2.3:a:denx:u-boot:2021.01:rc3:*:*:*:*:*:*
denx u-boot 2021.01 cpe:2.3:a:denx:u-boot:2021.01:rc4:*:*:*:*:*:*
denx u-boot 2021.01 cpe:2.3:a:denx:u-boot:2021.01:rc5:*:*:*:*:*:*
denx u-boot 2021.04 cpe:2.3:a:denx:u-boot:2021.04:rc1:*:*:*:*:*:*
denx u-boot 2021.04 cpe:2.3:a:denx:u-boot:2021.04:rc2:*:*:*:*:*:*
denx u-boot 2022.01 cpe:2.3:a:denx:u-boot:2022.01:-:*:*:*:*:*:*
denx u-boot 2022.01 cpe:2.3:a:denx:u-boot:2022.01:rc1:*:*:*:*:*:*
denx u-boot 2022.01 cpe:2.3:a:denx:u-boot:2022.01:rc2:*:*:*:*:*:*
denx u-boot 2022.01 cpe:2.3:a:denx:u-boot:2022.01:rc3:*:*:*:*:*:*
denx u-boot 2022.01 cpe:2.3:a:denx:u-boot:2022.01:rc4:*:*:*:*:*:*
denx u-boot 2022.04 cpe:2.3:a:denx:u-boot:2022.04:-:*:*:*:*:*:*
denx u-boot 2022.04 cpe:2.3:a:denx:u-boot:2022.04:rc1:*:*:*:*:*:*
denx u-boot 2022.04 cpe:2.3:a:denx:u-boot:2022.04:rc2:*:*:*:*:*:*
denx u-boot 2022.04 cpe:2.3:a:denx:u-boot:2022.04:rc3:*:*:*:*:*:*
denx u-boot 2022.04 cpe:2.3:a:denx:u-boot:2022.04:rc4:*:*:*:*:*:*
denx u-boot 2022.04 cpe:2.3:a:denx:u-boot:2022.04:rc5:*:*:*:*:*:*
denx u-boot 2022.07 cpe:2.3:a:denx:u-boot:2022.07:rc1:*:*:*:*:*:*
denx u-boot 2022.07 cpe:2.3:a:denx:u-boot:2022.07:rc2:*:*:*:*:*:*
denx u-boot 2022.07 cpe:2.3:a:denx:u-boot:2022.07:rc3:*:*:*:*:*:*
denx u-boot 2022.07 cpe:2.3:a:denx:u-boot:2022.07:rc4:*:*:*:*:*:*
denx u-boot 2022.07 cpe:2.3:a:denx:u-boot:2022.07:rc5:*:*:*:*:*:*

References for CVE-2022-33967

cvelogic Threat Intelligence