🛡️ openSUSE-SU-2021:1632-1 — chromium (CVE-2021-4098 +40 more)
Description
Security update for chromium
This update for chromium fixes the following issues:
Chromium 96.0.4664.110 (boo#1193713):
- CVE-2021-4098: Insufficient data validation in Mojo
- CVE-2021-4099: Use after free in Swiftshader
- CVE-2021-4100: Object lifecycle issue in ANGLE
- CVE-2021-4101: Heap buffer overflow in Swiftshader
- CVE-2021-4102: Use after free in V8
Lord of the Browsers: The Two Compilers:
- Go back to GCC
- GCC: LTO removes needed assembly symbols
- Clang: issues with libstdc++
Chromium 96.0.4664.93 (boo#1193519):
- CVE-2021-4052: Use after free in web apps
- CVE-2021-4053: Use after free in UI
- CVE-2021-4079: Out of bounds write in WebRTC
- CVE-2021-4054: Incorrect security UI in autofill
- CVE-2021-4078: Type confusion in V8
- CVE-2021-4055: Heap buffer overflow in extensions
- CVE-2021-4056: Type Confusion in loader
- CVE-2021-4057: Use after free in file API
- CVE-2021-4058: Heap buffer overflow in ANGLE
- CVE-2021-4059: Insufficient data validation in loader
- CVE-2021-4061: Type Confusion in V8
- CVE-2021-4062: Heap buffer overflow in BFCache
- CVE-2021-4063: Use after free in developer tools
- CVE-2021-4064: Use after free in screen capture
- CVE-2021-4065: Use after free in autofill
- CVE-2021-4066: Integer underflow in ANGLE
- CVE-2021-4067: Use after free in window manager
- CVE-2021-4068: Insufficient validation of untrusted input in new tab page
Chromium 96.0.4664.45 (boo#1192734):
- CVE-2021-38007: Type Confusion in V8
- CVE-2021-38008: Use after free in media
- CVE-2021-38009: Inappropriate implementation in cache
- CVE-2021-38006: Use after free in storage foundation
- CVE-2021-38005: Use after free in loader
- CVE-2021-38010: Inappropriate implementation in service workers
- CVE-2021-38011: Use after free in storage foundation
- CVE-2021-38012: Type Confusion in V8
- CVE-2021-38013: Heap buffer overflow in fingerprint recognition
- CVE-2021-38014: Out of bounds write in Swiftshader
- CVE-2021-38015: Inappropriate implementation in input
- CVE-2021-38016: Insufficient policy enforcement in background fetch
- CVE-2021-38017: Insufficient policy enforcement in iframe sandbox
- CVE-2021-38018: Inappropriate implementation in navigation
- CVE-2021-38019: Insufficient policy enforcement in CORS
- CVE-2021-38020: Insufficient policy enforcement in contacts picker
- CVE-2021-38021: Inappropriate implementation in referrer
- CVE-2021-38022: Inappropriate implementation in WebAuthentication
Affected software
openSUSE-SU-2021:1632-1 is recorded against 1 package.
- chromium (fixed in 96.0.4664.110-lp152.2.143.1)
Timeline and source
Published on 28 December 2021 and last revised on 4 February 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
lists.opensuse.org (Advisory)
bugzilla.suse.com (Report)
bugzilla.suse.com (Report)
bugzilla.suse.com (Report)
bugzilla.suse.com (Report)
www.suse.com (Web)
www.suse.com (Web)
www.suse.com (Web)
www.suse.com (Web)
www.suse.com (Web)
www.suse.com (Web)
www.suse.com (Web)
www.suse.com (Web)
www.suse.com (Web)
www.suse.com (Web)
Details
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| chromium | — | 96.0.4664.110-lp152.2.143.1 |
Similar Threats
- Unknown CGA-2297-w382-34r4
- Unknown CGA-243v-9v23-m9r5
- Unknown CGA-25cp-j993-p72w
- Unknown CGA-2622-vvq4-cvff
- Unknown CGA-26gp-q42g-399m
Free Vulnerability Check
Is your site affected by openSUSE-SU-2021:1632-1?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against openSUSE-SU-2021:1632-1 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.
