# CVE-2025-5222: Icu: stack buffer overflow in the srbroot::addtag function > A stack buffer overflow in the ICU library's genrb binary allows local attackers to execute arbitrary code via memory corruption. - **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 27 May 2025 - **Updated:** 21 Oct 2026 - **Also known as:** ALPINE-CVE-2025-5222, ALSA-2025:11888, ALSA-2025:12083, AZL-66147, AZL-66156, AZL-69692, AZL-69706, BELL-CVE-2025-5222, CLEANSTART-2026-GC28946, CLSA-2025-1762539763, CLSA-2026-1774269500, CLSA-2026-1774273758, CLSA-2026-1787152014, DEBIAN-CVE-2025-5222, DLA-4217-1, DSA-5951-1, ECHO-da2b-993e-93ac, GHSA-wv79-2fc4-v4hj, MGASA-2025-0249, OESA-2025-1982, RHSA-2025:11888, RHSA-2025:12083, RHSA-2025:12331, RHSA-2025:12332, RHSA-2025:12333, RLSA-2025:11888, RLSA-2025:12083, SUSE-SU-2025:02059-1, SUSE-SU-2025:02216-1, UBUNTU-CVE-2025-5222, openSUSE-SU-2025:15230-1 ## What is CVE-2025-5222? CVE-2025-5222 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 27 May 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description A stack buffer overflow was found in Internationl components for unicode (ICU ). While running the genrb binary, the 'subtag' struct overflowed at the SRBRoot::addTag function. This issue may lead to memory corruption and local arbitrary code execution. Weakness: CWE-120 (Buffer Copy without Checking Size of Input) ## Which versions are affected by CVE-2025-5222? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `icu` | AlmaLinux:10 | All versions | 74.2-5.el10_0 | | `libicu` | AlmaLinux:10 | All versions | 74.2-5.el10_0 | | `libicu-devel` | AlmaLinux:10 | All versions | 74.2-5.el10_0 | | `icu` | AlmaLinux:9 | All versions | 67.1-10.el9_6 | | `libicu` | AlmaLinux:9 | All versions | 67.1-10.el9_6 | | `libicu-devel` | AlmaLinux:9 | All versions | 67.1-10.el9_6 | | `icu` | Red Hat:enterprise_linux:10.0 | All versions | 0:74.2-5.el10_0 | | `icu-debuginfo` | Red Hat:enterprise_linux:10.0 | All versions | 0:74.2-5.el10_0 | | `icu-debugsource` | Red Hat:enterprise_linux:10.0 | All versions | 0:74.2-5.el10_0 | | `libicu` | Red Hat:enterprise_linux:10.0 | All versions | 0:74.2-5.el10_0 | | `libicu-debuginfo` | Red Hat:enterprise_linux:10.0 | All versions | 0:74.2-5.el10_0 | | `libicu-devel` | Red Hat:enterprise_linux:10.0 | All versions | 0:74.2-5.el10_0 | | `libicu-devel-debuginfo` | Red Hat:enterprise_linux:10.0 | All versions | 0:74.2-5.el10_0 | | `icu` | Red Hat:enterprise_linux:9::appstream | All versions | 0:67.1-10.el9_6 | | `icu-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:67.1-10.el9_6 | | `icu-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:67.1-10.el9_6 | | `libicu-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:67.1-10.el9_6 | | `libicu-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 0:67.1-10.el9_6 | | `libicu-devel-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:67.1-10.el9_6 | | `icu` | Red Hat:enterprise_linux:9::baseos | All versions | 0:67.1-10.el9_6 | | `icu-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:67.1-10.el9_6 | | `icu-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:67.1-10.el9_6 | | `libicu` | Red Hat:enterprise_linux:9::baseos | All versions | 0:67.1-10.el9_6 | | `libicu-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:67.1-10.el9_6 | | `libicu-devel-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:67.1-10.el9_6 | | `icu` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:67.1-10.el9_0 | | `icu-debuginfo` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:67.1-10.el9_0 | | `icu-debugsource` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:67.1-10.el9_0 | | `libicu-debuginfo` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:67.1-10.el9_0 | | `libicu-devel` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:67.1-10.el9_0 | | `libicu-devel-debuginfo` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:67.1-10.el9_0 | | `icu` | Red Hat:rhel_e4s:9.0::baseos | All versions | 0:67.1-10.el9_0 | | `icu-debuginfo` | Red Hat:rhel_e4s:9.0::baseos | All versions | 0:67.1-10.el9_0 | | `icu-debugsource` | Red Hat:rhel_e4s:9.0::baseos | All versions | 0:67.1-10.el9_0 | | `libicu` | Red Hat:rhel_e4s:9.0::baseos | All versions | 0:67.1-10.el9_0 | | `libicu-debuginfo` | Red Hat:rhel_e4s:9.0::baseos | All versions | 0:67.1-10.el9_0 | | `libicu-devel-debuginfo` | Red Hat:rhel_e4s:9.0::baseos | All versions | 0:67.1-10.el9_0 | | `icu` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:67.1-10.el9_2 | | `icu-debuginfo` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:67.1-10.el9_2 | | `icu-debugsource` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:67.1-10.el9_2 | Products: Unicode International Components for Unicode. ## How do I fix CVE-2025-5222? Apply the vendor's patch. ## Is CVE-2025-5222 being exploited? There is no known exploitation of CVE-2025-5222 in the wild and no public exploit code. Public exploit code: - Debian build files for icu 74.2 with a patch to fix CVE-2025-5222 (github_poc): https://github.com/berkley4/icu-74-debian ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-5222 and fix it if it is affected. What it is: CVE-2025-5222 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 27 May 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2025-5222 in the wild and no public exploit code. Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-5222/ (Markdown: https://insights.sbomify.com/CVE-2025-5222/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-5222 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-5222 - OSV: https://osv.dev/vulnerability/CVE-2025-5222 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-5222/ Summaries are generated and may contain mistakes; the official description above is the record.