Debian LinuxOperating system · Debian
CVE-2022-0544
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn integer underflow in the DDS loader of Blender leads to an out-of-bounds read, possibly allowing an attacker to read sensitive data using a crafted DDS image file. This flaw affects Blender versions prior to 2.83.19, 2.93.8 and 3.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAn integer underflow vulnerability in Blender's DDS image file loader causes an out-of-bounds read when parsing crafted DDS files, potentially allowing attackers to read sensitive memory contents beyond allocated buffers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Debian LinuxOperating system
= 9.0= 10.0< 2.83.19>= 2.90.0, < 2.93.8>= 3.0, < 3.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Blender versionOpen Blender and go to Help > About Blender, or run 'blender --version' from command line. Note the version number displayed.Affected if The version is less than 2.83.19, OR between 2.90.0 and 2.93.7 inclusive, OR between 3.0.0 and 3.0.x inclusive
-
Check Debian Blender package versionRun 'dpkg -l | grep blender' or 'apt-cache policy blender' on Debian systems to see the installed package version.Affected if On Debian 9 or 10, the installed blender package version is earlier than the fixed versions for those releases
-
Verify DDS file loading capability is accessibleIn Blender, try to import a DDS file via File > Import > DDS, or check if the DDS import addon is enabled in Edit > Preferences > Add-ons.Affected if DDS import functionality is available and the Blender version falls within the affected ranges above
You are affected if you use Blender versions 2.83.x below 2.83.19, 2.90.x through 2.93.7, or 3.0.x through 3.0.x and have the ability to load DDS image files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.83.192.93.83.1
Update Blender to version 2.83.19, 2.93.8, or 3.1 or later to obtain the patched DDS loader with proper integer bounds checking.
Blender 2.83.19 (LTS), 2.93.8 (stable), or 3.1+ (select based on your current major version)
- Identify your current Blender version from the Help > About Blender menu
- Close Blender completely before upgrading
- Download Blender version 2.83.19 or later from the 2.83 LTS series, OR version 2.93.8 or later from the 2.93 stable series, OR version 3.1 or later from the 3.x series
- Run the downloaded installer and follow the prompts to install the new version
- Launch Blender and verify the application starts without errors
- Test loading a DDS image file to confirm the DDS loader functions correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0544 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-0544 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data