Security readout for executives and security teams
Plain-English summary
SDL2 has a memory leak in texture creation for its GLES renderer. Sources state an unauthenticated attacker could cause denial of service by exhausting availability. This matters for applications that bundle or depend on affected SDL2 versions.
Executive priority
Treat as a high-priority availability risk where SDL2 is used in exposed services or high-reliability applications. It is less urgent for isolated desktop-only use, but still should be patched through normal dependency maintenance.
Technical view
CVE-2022-4743 is CWE-401 in SDL2's GLES_CreateTexture() within SDL_render_gles.c. The record lists SDL2 v2.0.4 and above as affected, with fixes in sdl-2.26.0 and sdl-prerelease-2.25.1. CVSS 3.1 is 7.5: network, low complexity, no privileges, no user interaction, availability impact only.
Likely exposure
Exposure is most likely in applications or distributions using SDL2 2.0.4 or later before the fixed release, especially where SDL2 handles remotely influenced rendering workloads. SDL-1.x is explicitly not affected.
Exploitation context
The bundle does not cite active exploitation, and the CVE is not marked CISA KEV. The documented impact is denial of service through memory leakage, not confidentiality or integrity compromise.
Researcher notes
The source bundle identifies the vulnerable function and fixed upstream release, but does not provide detailed trigger conditions or proof of exploitation. Validate exposure by version, linkage model, vendor backports, and whether GLES texture creation is reachable in the application.
Mitigation direction
- Upgrade SDL2 to 2.26.0 or a vendor-fixed package.
- Apply relevant Debian, Gentoo, Red Hat, or upstream SDL guidance.
- Rebuild applications that bundle a vulnerable SDL2 copy.
- Prioritize externally reachable or service-facing rendering workloads.
- If upgrade timing is blocked, follow vendor mitigation guidance.
Validation and detection
- Inventory system and bundled SDL2 versions across affected assets.
- Confirm SDL2 is 2.26.0 or vendor-patched equivalent.
- Check SBOMs and package manifests for embedded SDL2 copies.
- Identify apps using SDL2 GLES rendering paths.
- Verify vulnerability scanners map findings to fixed package versions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-4743 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://bugzilla.redhat.com/show_bug.cgi?id=2156290CVE reference
- https://access.redhat.com/security/cve/CVE-2022-4743CVE reference
- https://github.com/libsdl-org/SDL/pull/6269CVE reference
- https://github.com/libsdl-org/SDL/commit/00b67f55727bc0944c3266e2b875440da132ce4bCVE reference
- [debian-lts-announce] 20230208 [SECURITY] [DLA 3314-1] libsdl2 security updateCVE reference · mailing-list
- GLSA-202305-18CVE reference · vendor-advisory
- https://lists.debian.org/debian-lts-announce/2025/11/msg00024.htmlCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
