rootless: `/sys/fs/cgroup` is writable when cgroupns isn't unshared in runc
cve-program · CVE-2023-25809
Publishedrunc is a CLI tool for spawning and running containers according to the OCI specification. In affected versions it was found that rootless runc makes `/sys/fs/cgroup` writable in following conditons: 1. when runc is executed inside the user namespace, and the `config.json` does not specify the cgroup namespace to be unshared (e.g.., `(docker|podman|nerdctl) run --cgroupns=host`, with Rootless Docker/Podman/nerdctl) or 2. when runc is executed outside the user namespace, and `/sys` is mounted with `rbind, ro` (e.g., `runc spec --rootless`; this condition is very rare). A container may gain the write access to user-owned cgroup hierarchy `/sys/fs/cgroup/user.slice/...` on the host . Other users's cgroup hierarchies are not affected. Users are advised to upgrade to version 1.1.5. Users unable to upgrade may unshare the cgroup namespace (`(docker|podman|nerdctl) run --cgroupns=private)`. This is the default behavior of Docker/Podman/nerdctl on cgroup v2 hosts. or add `/sys/fs/cgroup` to `maskedPaths`.
Read the publisher's advisoryeuvd · EUVD-2023-1058
Publishedrunc is a CLI tool for spawning and running containers according to the OCI specification. In affected versions it was found that rootless runc makes `/sys/fs/cgroup` writable in following conditons: 1. when runc is executed inside the user namespace, and the `config.json` does not specify the cgroup namespace to be unshared (e.g.., `(docker|podman|nerdctl) run --cgroupns=host`, with Rootless Docker/Podman/nerdctl) or 2. when runc is executed outside the user namespace, and `/sys` is mounted with `rbind, ro` (e.g., `runc spec --rootless`; this condition is very rare). A container may gain the write access to user-owned cgroup hierarchy `/sys/fs/cgroup/user.slice/...` on the host . Other users's cgroup hierarchies are not affected. Users are advised to upgrade to version 1.1.5. Users unable to upgrade may unshare the cgroup namespace (`(docker|podman|nerdctl) run --cgroupns=private)`. This is the default behavior of Docker/Podman/nerdctl on cgroup v2 hosts. or add `/sys/fs/cgroup` to `maskedPaths`.
Read the publisher's advisorynvd · CVE-2023-25809
Publishedrunc is a CLI tool for spawning and running containers according to the OCI specification. In affected versions it was found that rootless runc makes `/sys/fs/cgroup` writable in following conditons: 1. when runc is executed inside the user namespace, and the `config.json` does not specify the cgroup namespace to be unshared (e.g.., `(docker|podman|nerdctl) run --cgroupns=host`, with Rootless Docker/Podman/nerdctl) or 2. when runc is executed outside the user namespace, and `/sys` is mounted with `rbind, ro` (e.g., `runc spec --rootless`; this condition is very rare). A container may gain the write access to user-owned cgroup hierarchy `/sys/fs/cgroup/user.slice/...` on the host . Other users's cgroup hierarchies are not affected. Users are advised to upgrade to version 1.1.5. Users unable to upgrade may unshare the cgroup namespace (`(docker|podman|nerdctl) run --cgroupns=private)`. This is the default behavior of Docker/Podman/nerdctl on cgroup v2 hosts. or add `/sys/fs/cgroup` to `maskedPaths`.
Read the publisher's advisoryosv · GHSA-m8cg-xc2p-r3fc
Published### Impact It was found that rootless runc makes `/sys/fs/cgroup` writable in following conditons: 1. when runc is executed inside the user namespace, and the `config.json` does not specify the cgroup namespace to be unshared (e.g.., `(docker|podman|nerdctl) run --cgroupns=host`, with Rootless Docker/Podman/nerdctl) 2. or, when runc is executed outside the user namespace, and `/sys` is mounted with `rbind, ro` (e.g., `runc spec --rootless`; this condition is very rare) A container may gain the write access to user-owned cgroup hierarchy `/sys/fs/cgroup/user.slice/...` on the host . Other users's cgroup hierarchies are not affected. ### Patches v1.1.5 (planned) ### Workarounds - Condition 1: Unshare the cgroup namespace (`(docker|podman|nerdctl) run --cgroupns=private)`. This is the default behavior of Docker/Podman/nerdctl on cgroup v2 hosts. - Condition 2 (very rare): add `/sys/fs/cgroup` to `maskedPaths`
Read the publisher's advisoryosv · GO-2023-1682
PublishedRootless: /sys/fs/cgroup is writable when cgroupns isn't unshared in github.com/opencontainers/runc
Read the publisher's advisoryAffected versions, risk and source history
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2023-25809
Publishedrootless: `/sys/fs/cgroup` is writable when cgroupns isn't unshared in runc
runc is a CLI tool for spawning and running containers according to the OCI specification. In affected versions it was found that rootless runc makes `/sys/fs/cgroup` writable in following conditons: 1. when runc is executed inside the user namespace, and the `config.json` does not specify the cgroup namespace to be unshared (e.g.., `(docker|podman|nerdctl) run --cgroupns=host`, with Rootless Docker/Podman/nerdctl) or 2. when runc is executed outside the user namespace, and `/sys` is mounted with `rbind, ro` (e.g., `runc spec --rootless`; this condition is very rare). A container may gain the write access to user-owned cgroup hierarchy `/sys/fs/cgroup/user.slice/...` on the host . Other users's cgroup hierarchies are not affected. Users are advised to upgrade to version 1.1.5. Users unable to upgrade may unshare the cgroup namespace (`(docker|podman|nerdctl) run --cgroupns=private)`. This is the default behavior of Docker/Podman/nerdctl on cgroup v2 hosts. or add `/sys/fs/cgroup` to `maskedPaths`.
- Source published
- 29 Mar 2023 18:22:56 UTC
- Source modified
- 12 Feb 2025 16:02:24 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · 5.0 CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:L
euvd · EUVD-2023-1058
Publishedrunc is a CLI tool for spawning and running containers according to the OCI specification. In affected versions it was found that rootless runc makes `/sys/fs/cgroup` writable in following conditons: 1. when runc is executed inside the user…
runc is a CLI tool for spawning and running containers according to the OCI specification. In affected versions it was found that rootless runc makes `/sys/fs/cgroup` writable in following conditons: 1. when runc is executed inside the user namespace, and the `config.json` does not specify the cgroup namespace to be unshared (e.g.., `(docker|podman|nerdctl) run --cgroupns=host`, with Rootless Docker/Podman/nerdctl) or 2. when runc is executed outside the user namespace, and `/sys` is mounted with `rbind, ro` (e.g., `runc spec --rootless`; this condition is very rare). A container may gain the write access to user-owned cgroup hierarchy `/sys/fs/cgroup/user.slice/...` on the host . Other users's cgroup hierarchies are not affected. Users are advised to upgrade to version 1.1.5. Users unable to upgrade may unshare the cgroup namespace (`(docker|podman|nerdctl) run --cgroupns=private)`. This is the default behavior of Docker/Podman/nerdctl on cgroup v2 hosts. or add `/sys/fs/cgroup` to `maskedPaths`.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Mar 29, 2023, 6:22:56 PM
dateUpdated: Feb 12, 2025, 4:02:24 PM
11 related source bulletins · separate from aliases
openSUSE-SU-2025:15424-1: govulncheck-vulndb-0.0.20250807T150727-1.1 on GA media
CVE-2015-7561 · CVE-2016-9962 · CVE-2017-1000056 · CVE-2017-1002102 · CVE-2018-1002100 · CVE-2018-1002101 · CVE-2018-16733 · CVE-2018-19184 · CVE-2019-1002100 · CVE-2019-1002101 · CVE-2019-11245 · CVE-2019-11251 · CVE-2019-11253 · CVE-2020-26240 · CVE-2020-26241 · CVE-2020-8551 · CVE-2020-8555 · CVE-2020-8557 · CVE-2020-8558 · CVE-2020-8562 · CVE-2020-8563 · CVE-2020-8566 · CVE-2021-25735 · CVE-2021-25736 · CVE-2021-25737 · CVE-2021-25741 · CVE-2021-25743 · CVE-2021-30465 · CVE-2022-29162 · CVE-2022-29177 · CVE-2022-3162 · CVE-2022-3294 · CVE-2023-2431 · CVE-2023-25809 · CVE-2023-2727 · CVE-2023-2728 · CVE-2023-27561 · CVE-2023-28642 · CVE-2023-5528 · CVE-2024-45310 · CVE-2024-5321 · CVE-2025-3445 · CVE-2025-47907 · CVE-2025-47908
msrc_CVE-2023-25809: rootless: `/sys/fs/cgroup` is writable when cgroupns isn't unshared in runc
CVE-2023-25809
WID-SEC-W-2024-0794: Dell ECS: Mehrere Schwachstellen
CVE-2018-18074 · CVE-2020-10663 · CVE-2020-10672 · CVE-2020-10673 · CVE-2020-10735 · CVE-2020-10968 · CVE-2020-10969 · CVE-2020-11111 · CVE-2020-11112 · CVE-2020-11113 · CVE-2020-11612 · CVE-2020-11619 · CVE-2020-11620 · CVE-2020-11979 · CVE-2020-12762 · CVE-2020-12825 · CVE-2020-13956 · CVE-2020-14060 · CVE-2020-14061 · CVE-2020-14062 · CVE-2020-14195 · CVE-2020-15250 · CVE-2020-1945 · CVE-2020-1967 · CVE-2020-1971 · CVE-2020-24616 · CVE-2020-24750 · CVE-2020-25649 · CVE-2020-25658 · CVE-2020-26116 · CVE-2020-26137 · CVE-2020-26541 · CVE-2020-27216 · CVE-2020-27218 · CVE-2020-27223 · CVE-2020-28366 · CVE-2020-28493 · CVE-2020-29509 · CVE-2020-29511 · CVE-2020-29582 · CVE-2020-29651 · CVE-2020-35490 · CVE-2020-35491 · CVE-2020-35728 · CVE-2020-36179 · CVE-2020-36180 · CVE-2020-36181 · CVE-2020-36182 · CVE-2020-36183 · CVE-2020-36184 · CVE-2020-36185 · CVE-2020-36186 · CVE-2020-36187 · CVE-2020-36188 · CVE-2020-36189 · CVE-2020-36516 · CVE-2020-36518 · CVE-2020-36557 · CVE-2020-36558 · CVE-2020-36691 · CVE-2020-7238 · CVE-2020-8840 · CVE-2020-8908 · CVE-2020-8911 · CVE-2020-8912 · CVE-2020-9488 · CVE-2020-9493 · CVE-2020-9546 · CVE-2020-9547 · CVE-2020-9548 · CVE-2021-20190 · CVE-2021-20323 · CVE-2021-21290 · CVE-2021-21295 · CVE-2021-21409 · CVE-2021-23840 · CVE-2021-23841 · CVE-2021-2471 · CVE-2021-25642 · CVE-2021-26341 · CVE-2021-27918 · CVE-2021-28153 · CVE-2021-28165 · CVE-2021-28169 · CVE-2021-28861 · CVE-2021-29425 · CVE-2021-30560 · CVE-2021-3114 · CVE-2021-33036 · CVE-2021-33194 · CVE-2021-33195 · CVE-2021-33196 · CVE-2021-33197 · CVE-2021-33503 · CVE-2021-33655 · CVE-2021-33656 · CVE-2021-3424 · CVE-2021-34428 · CVE-2021-3449 · CVE-2021-3450 · CVE-2021-3530 · CVE-2021-36221 · CVE-2021-36373 · CVE-2021-36374 · CVE-2021-3648 · CVE-2021-36690 · CVE-2021-3711 · CVE-2021-3712 · CVE-2021-37136 · CVE-2021-37137 · CVE-2021-37404 · CVE-2021-37533 · CVE-2021-3754 · CVE-2021-3778 · CVE-2021-3796 · CVE-2021-3826 · CVE-2021-3827 · CVE-2021-38297 · CVE-2021-3872 · CVE-2021-3875 · CVE-2021-3903 · CVE-2021-3923 · CVE-2021-3927 · CVE-2021-3928 · CVE-2021-3968 · CVE-2021-3973 · CVE-2021-3974 · CVE-2021-3984 · CVE-2021-4019 · CVE-2021-4037 · CVE-2021-4069 · CVE-2021-4104 · CVE-2021-4136 · CVE-2021-4157 · CVE-2021-4166 · CVE-2021-41771 · CVE-2021-4192 · CVE-2021-4193 · CVE-2021-4203 · CVE-2021-42567 · CVE-2021-43797 · CVE-2021-44531 · CVE-2021-44532 · CVE-2021-44533 · CVE-2021-44716 · CVE-2021-44878 · CVE-2021-45078 · CVE-2021-46195 · CVE-2021-46828 · CVE-2021-46848 · CVE-2022-0128 · CVE-2022-0213 · CVE-2022-0225 · CVE-2022-0261 · CVE-2022-0318 · CVE-2022-0319 · CVE-2022-0351 · CVE-2022-0359 · CVE-2022-0361 · CVE-2022-0392 · CVE-2022-0407 · CVE-2022-0413 · CVE-2022-0561 · CVE-2022-0696 · CVE-2022-0778 · CVE-2022-1184 · CVE-2022-1245 · CVE-2022-1271 · CVE-2022-1292 · CVE-2022-1381 · CVE-2022-1420 · CVE-2022-1462 · CVE-2022-1466 · CVE-2022-1471 · CVE-2022-1586 · CVE-2022-1587 · CVE-2022-1616 · CVE-2022-1619 · CVE-2022-1620 · CVE-2022-1679 · CVE-2022-1705 · CVE-2022-1720 · CVE-2022-1729 · CVE-2022-1733 · CVE-2022-1735 · CVE-2022-1771 · CVE-2022-1785 · CVE-2022-1796 · CVE-2022-1851 · CVE-2022-1897 · CVE-2022-1898 · CVE-2022-1927 · CVE-2022-1962 · CVE-2022-1968 · CVE-2022-1974 · CVE-2022-1975 · CVE-2022-20132 · CVE-2022-20141 · CVE-2022-20154 · CVE-2022-20166 · CVE-2022-20368 · CVE-2022-20369 · CVE-2022-2047 · CVE-2022-2048 · CVE-2022-20567 · CVE-2022-2068 · CVE-2022-2097 · CVE-2022-21216 · CVE-2022-21233 · CVE-2022-2124 · CVE-2022-2125 · CVE-2022-2126 · CVE-2022-2129 · CVE-2022-21363 · CVE-2022-21385 · CVE-2022-21499 · CVE-2022-2153 · CVE-2022-21540 · CVE-2022-21541 · CVE-2022-21549 · CVE-2022-21618 · CVE-2022-21619 · CVE-2022-21624 · CVE-2022-21626 · CVE-2022-21628 · CVE-2022-21702 · CVE-2022-2175 · CVE-2022-2182 · CVE-2022-2183 · CVE-2022-2206 · CVE-2022-2207 · CVE-2022-2208 · CVE-2022-2210 · CVE-2022-2231 · CVE-2022-2256 · CVE-2022-2257 · CVE-2022-2264 · CVE-2022-2284 · CVE-2022-2285 · CVE-2022-2286 · CVE-2022-2287 · CVE-2022-22976 · CVE-2022-22978 · CVE-2022-2304 · CVE-2022-2318 · CVE-2022-23302 · CVE-2022-23305 · CVE-2022-23307 · CVE-2022-2343 · CVE-2022-2344 · CVE-2022-2345 · CVE-2022-23471 · CVE-2022-23521 · CVE-2022-23772 · CVE-2022-23773 · CVE-2022-24302 · CVE-2022-24329 · CVE-2022-24823 · CVE-2022-24903 · CVE-2022-2503 · CVE-2022-25147 · CVE-2022-25168 · CVE-2022-2519 · CVE-2022-2520 · CVE-2022-2521 · CVE-2022-2522 · CVE-2022-25647 · CVE-2022-2571 · CVE-2022-2580 · CVE-2022-2581 · CVE-2022-25857 · CVE-2022-2588 · CVE-2022-2598 · CVE-2022-26148 · CVE-2022-26365 · CVE-2022-26373 · CVE-2022-2639 · CVE-2022-26612 · CVE-2022-2663 · CVE-2022-27781 · CVE-2022-27782 · CVE-2022-27943 · CVE-2022-2795 · CVE-2022-28131 · CVE-2022-2816 · CVE-2022-2817 · CVE-2022-2819 · CVE-2022-28327 · CVE-2022-2845 · CVE-2022-2849 · CVE-2022-2862 · CVE-2022-2867 · CVE-2022-2868 · CVE-2022-2869 · CVE-2022-28693 · CVE-2022-2874 · CVE-2022-28748 · CVE-2022-2880 · CVE-2022-2889 · CVE-2022-29162 · CVE-2022-29187 · CVE-2022-2923 · CVE-2022-2946 · CVE-2022-29526 · CVE-2022-29583 · CVE-2022-2964 · CVE-2022-2977 · CVE-2022-2980 · CVE-2022-2982 · CVE-2022-29900 · CVE-2022-29901 · CVE-2022-2991 · CVE-2022-3016 · CVE-2022-3028 · CVE-2022-3037 · CVE-2022-30580 · CVE-2022-30630 · CVE-2022-30631 · CVE-2022-30632 · CVE-2022-30633 · CVE-2022-3099 · CVE-2022-31030 · CVE-2022-31159 · CVE-2022-3134 · CVE-2022-3153 · CVE-2022-3169 · CVE-2022-31690 · CVE-2022-32148 · CVE-2022-32149 · CVE-2022-32206 · CVE-2022-32208 · CVE-2022-32221 · CVE-2022-3234 · CVE-2022-3235 · CVE-2022-3239 · CVE-2022-3278 · CVE-2022-3296 · CVE-2022-3297 · CVE-2022-33196 · CVE-2022-3324 · CVE-2022-3352 · CVE-2022-33740 · CVE-2022-33741 · CVE-2022-33742 · CVE-2022-33972 · CVE-2022-33981 · CVE-2022-34169 · CVE-2022-3424 · CVE-2022-34266 · CVE-2022-34526 · CVE-2022-34903 · CVE-2022-3491 · CVE-2022-3515 · CVE-2022-3520 · CVE-2022-3521 · CVE-2022-3524 · CVE-2022-35252 · CVE-2022-3542 · CVE-2022-3545 · CVE-2022-3564 · CVE-2022-3565 · CVE-2022-3566 · CVE-2022-3567 · CVE-2022-35737 · CVE-2022-3586 · CVE-2022-3591 · CVE-2022-3594 · CVE-2022-3597 · CVE-2022-3599 · CVE-2022-36109 · CVE-2022-3621 · CVE-2022-3626 · CVE-2022-3627 · CVE-2022-3628 · CVE-2022-36280 · CVE-2022-3629 · CVE-2022-3635 · CVE-2022-3643 · CVE-2022-36437 · CVE-2022-3646 · CVE-2022-3649 · CVE-2022-36760 · CVE-2022-36879 · CVE-2022-36946 · CVE-2022-3705 · CVE-2022-37434 · CVE-2022-37436 · CVE-2022-37865 · CVE-2022-37866 · CVE-2022-38090 · CVE-2022-38096 · CVE-2022-38126 · CVE-2022-38127 · CVE-2022-38177 · CVE-2022-38178 · CVE-2022-3821 · CVE-2022-38533 · CVE-2022-38749 · CVE-2022-38750 · CVE-2022-38751 · CVE-2022-38752 · CVE-2022-39028 · CVE-2022-3903 · CVE-2022-39188 · CVE-2022-39399 · CVE-2022-3970 · CVE-2022-40149 · CVE-2022-40150 · CVE-2022-40151 · CVE-2022-40152 · CVE-2022-40153 · CVE-2022-40303 · CVE-2022-40304 · CVE-2022-40307 · CVE-2022-40674 · CVE-2022-40768 · CVE-2022-40899 · CVE-2022-4095 · CVE-2022-41218 · CVE-2022-4129 · CVE-2022-4141 · CVE-2022-41717 · CVE-2022-41721 · CVE-2022-41848 · CVE-2022-41850 · CVE-2022-41854 · CVE-2022-41858 · CVE-2022-41881 · CVE-2022-41903 · CVE-2022-41915 · CVE-2022-41966 · CVE-2022-41974 · CVE-2022-42003 · CVE-2022-42004 · CVE-2022-42010 · CVE-2022-42011 · CVE-2022-42012 · CVE-2022-42328 · CVE-2022-42329 · CVE-2022-42703 · CVE-2022-42889 · CVE-2022-42895 · CVE-2022-42896 · CVE-2022-42898 · CVE-2022-4292 · CVE-2022-4293 · CVE-2022-42969 · CVE-2022-4304 · CVE-2022-43552 · CVE-2022-43680 · CVE-2022-43750 · CVE-2022-4378 · CVE-2022-43945 · CVE-2022-43995 · CVE-2022-4415 · CVE-2022-4450 · CVE-2022-44638 · CVE-2022-45061 · CVE-2022-45688 · CVE-2022-45884 · CVE-2022-45885 · CVE-2022-45886 · CVE-2022-45887 · CVE-2022-45919 · CVE-2022-45934 · CVE-2022-45939 · CVE-2022-4662 · CVE-2022-46751 · CVE-2022-46908 · CVE-2022-47629 · CVE-2022-47929 · CVE-2022-48281 · CVE-2022-48337 · CVE-2022-48339 · CVE-2023-0045 · CVE-2023-0049 · CVE-2023-0051 · CVE-2023-0054 · CVE-2023-0215 · CVE-2023-0286 · CVE-2023-0288 · CVE-2023-0433 · CVE-2023-0464 · CVE-2023-0465 · CVE-2023-0466 · CVE-2023-0512 · CVE-2023-0590 · CVE-2023-0597 · CVE-2023-0833 · CVE-2023-1076 · CVE-2023-1095 · CVE-2023-1118 · CVE-2023-1127 · CVE-2023-1170 · CVE-2023-1175 · CVE-2023-1370 · CVE-2023-1380 · CVE-2023-1390 · CVE-2023-1436 · CVE-2023-1513 · CVE-2023-1611 · CVE-2023-1670 · CVE-2023-1855 · CVE-2023-1989 · CVE-2023-1990 · CVE-2023-1998 · CVE-2023-20862 · CVE-2023-2124 · CVE-2023-2162 · CVE-2023-2176 · CVE-2023-21830 · CVE-2023-21835 · CVE-2023-21843 · CVE-2023-21930 · CVE-2023-21937 · CVE-2023-21938 · CVE-2023-21939 · CVE-2023-2194 · CVE-2023-21954 · CVE-2023-21967 · CVE-2023-21968 · CVE-2023-22490 · CVE-2023-2253 · CVE-2023-22809 · CVE-2023-23454 · CVE-2023-23455 · CVE-2023-23559 · CVE-2023-23916 · CVE-2023-23946 · CVE-2023-24329 · CVE-2023-24532 · CVE-2023-24534 · CVE-2023-2483 · CVE-2023-24998 · CVE-2023-2513 · CVE-2023-25193 · CVE-2023-25652 · CVE-2023-25690 · CVE-2023-25809 · CVE-2023-25815 · CVE-2023-26048 · CVE-2023-26049 · CVE-2023-2650 · CVE-2023-26545 · CVE-2023-26604 · CVE-2023-27533 · CVE-2023-27534 · CVE-2023-27535 · CVE-2023-27536 · CVE-2023-27538 · CVE-2023-27561 · CVE-2023-2828 · CVE-2023-28320 · CVE-2023-28321 · CVE-2023-28322 · CVE-2023-28328 · CVE-2023-28464 · CVE-2023-28486 · CVE-2023-28487 · CVE-2023-28642 · CVE-2023-28772 · CVE-2023-28840 · CVE-2023-28841 · CVE-2023-28842 · CVE-2023-29007 · CVE-2023-29383 · CVE-2023-29402 · CVE-2023-29406 · CVE-2023-29409 · CVE-2023-2976 · CVE-2023-30630 · CVE-2023-30772 · CVE-2023-31084 · CVE-2023-3138 · CVE-2023-31436 · CVE-2023-31484 · CVE-2023-32269 · CVE-2023-32697 · CVE-2023-33264 · CVE-2023-34034 · CVE-2023-34035 · CVE-2023-34453 · CVE-2023-34454 · CVE-2023-34455 · CVE-2023-34462 · CVE-2023-35116 · CVE-2023-3635 · CVE-2023-36479 · CVE-2023-39533 · CVE-2023-40167 · CVE-2023-40217 · CVE-2023-41105 · CVE-2023-41900 · CVE-2023-43642 · CVE-2023-43804 · CVE-2023-44487 · CVE-2023-45803 · CVE-2024-21626
WID-SEC-W-2023-1183: docker: Mehrere Schwachstellen
CVE-2023-24532 · CVE-2023-25809 · CVE-2023-27561 · CVE-2023-28642 · CVE-2023-28840 · CVE-2023-28841 · CVE-2023-28842
openSUSE-SU-2024:12826-1: runc-1.1.5-1.1 on GA media
CVE-2023-25809 · CVE-2023-27561 · CVE-2023-28642
SUSE-SU-2023:2003-1: Security update for runc
CVE-2023-25809 · CVE-2023-27561 · CVE-2023-28642
RHSA-2023:1326: Red Hat Security Advisory: OpenShift Container Platform 4.13.0 security update
CVE-2021-4235 · CVE-2021-4238 · CVE-2021-20329 · CVE-2021-38561 · CVE-2022-21698 · CVE-2022-23525 · CVE-2022-23526 · CVE-2022-27191 · CVE-2022-41316 · CVE-2022-41717 · CVE-2022-41721 · CVE-2022-41723 · CVE-2022-41724 · CVE-2022-41725 · CVE-2022-46146 · CVE-2023-0620 · CVE-2023-0665 · CVE-2023-25000 · CVE-2023-25165 · CVE-2023-25173 · CVE-2023-25809 · CVE-2023-27561 · CVE-2023-28642 · CVE-2023-30841
SUSE-SU-2023:1726-1: Security update for runc
CVE-2023-25809 · CVE-2023-27561 · CVE-2023-28642
RHSA-2023:6380: Red Hat Security Advisory: runc security update
CVE-2021-43784 · CVE-2022-41724 · CVE-2023-25809 · CVE-2023-27561 · CVE-2023-28642
RHSA-2023:6939: Red Hat Security Advisory: container-tools:rhel8 security and bug fix update
CVE-2022-3064 · CVE-2022-41723 · CVE-2022-41724 · CVE-2022-41725 · CVE-2023-3978 · CVE-2023-24534 · CVE-2023-24536 · CVE-2023-24537 · CVE-2023-24538 · CVE-2023-24539 · CVE-2023-24540 · CVE-2023-25173 · CVE-2023-25809 · CVE-2023-27561 · CVE-2023-28642 · CVE-2023-29400 · CVE-2023-29406
RHSA-2023:6938: Red Hat Security Advisory: container-tools:4.0 security and bug fix update
CVE-2022-3064 · CVE-2022-41723 · CVE-2022-41724 · CVE-2022-41725 · CVE-2023-3978 · CVE-2023-24534 · CVE-2023-24536 · CVE-2023-24537 · CVE-2023-24538 · CVE-2023-24539 · CVE-2023-24540 · CVE-2023-25809 · CVE-2023-27561 · CVE-2023-28642 · CVE-2023-29400 · CVE-2023-29406
- Source published
- Mar 29, 2023, 6:22:56 PM (timezone not stated)
- Source modified
- Feb 12, 2025, 4:02:24 PM (timezone not stated)
- Saved here
- 18 Nov 2026 04:32:56 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 3.1 · 5.0 CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:L
nvd · CVE-2023-25809
Publishedrunc is a CLI tool for spawning and running containers according to the OCI specification. In affected versions it was found that rootless runc makes `/sys/fs/cgroup` writable in following conditons: 1. when runc is executed inside the user…
runc is a CLI tool for spawning and running containers according to the OCI specification. In affected versions it was found that rootless runc makes `/sys/fs/cgroup` writable in following conditons: 1. when runc is executed inside the user namespace, and the `config.json` does not specify the cgroup namespace to be unshared (e.g.., `(docker|podman|nerdctl) run --cgroupns=host`, with Rootless Docker/Podman/nerdctl) or 2. when runc is executed outside the user namespace, and `/sys` is mounted with `rbind, ro` (e.g., `runc spec --rootless`; this condition is very rare). A container may gain the write access to user-owned cgroup hierarchy `/sys/fs/cgroup/user.slice/...` on the host . Other users's cgroup hierarchies are not affected. Users are advised to upgrade to version 1.1.5. Users unable to upgrade may unshare the cgroup namespace (`(docker|podman|nerdctl) run --cgroupns=private)`. This is the default behavior of Docker/Podman/nerdctl on cgroup v2 hosts. or add `/sys/fs/cgroup` to `maskedPaths`.
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Modified
Weakness classifications: CWE-281
Original publisher date fields
published: 2023-03-29T19:15:22.170
lastModified: 2026-06-17T05:42:01.917
1 source CPE criteria · context only
- cpe:2.3:a:linuxfoundation:runc:*:*:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 29 Mar 2023 19:15:22 UTC
- Source modified
- 17 Jun 2026 05:42:01 UTC
- Saved here
- 24 Oct 2026 21:17:28 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · [email protected] · Secondary · 5.0 CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:L
CVSS 3.1 · [email protected] · Primary · 6.3 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
osv · GHSA-m8cg-xc2p-r3fc
Publishedrootless: `/sys/fs/cgroup` is writable when cgroupns isn't unshared in runc
### Impact It was found that rootless runc makes `/sys/fs/cgroup` writable in following conditons: 1. when runc is executed inside the user namespace, and the `config.json` does not specify the cgroup namespace to be unshared (e.g.., `(docker|podman|nerdctl) run --cgroupns=host`, with Rootless Docker/Podman/nerdctl) 2. or, when runc is executed outside the user namespace, and `/sys` is mounted with `rbind, ro` (e.g., `runc spec --rootless`; this condition is very rare) A container may gain the write access to user-owned cgroup hierarchy `/sys/fs/cgroup/user.slice/...` on the host . Other users's cgroup hierarchies are not affected. ### Patches v1.1.5 (planned) ### Workarounds - Condition 1: Unshare the cgroup namespace (`(docker|podman|nerdctl) run --cgroupns=private)`. This is the default behavior of Docker/Podman/nerdctl on cgroup v2 hosts. - Condition 2 (very rare): add `/sys/fs/cgroup` to `maskedPaths`
- Source published
- 30 Mar 2023 20:17:24 UTC
- Source modified
- 10 Sep 2026 03:49:53 UTC
- Saved here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:N/I:N/A:L
Publisher rating · LOW
osv · GO-2023-1682
PublishedRootless: /sys/fs/cgroup is writable when cgroupns isn't unshared in github.com/opencontainers/runc
Rootless: /sys/fs/cgroup is writable when cgroupns isn't unshared in github.com/opencontainers/runc
- Source published
- 20 Aug 2024 20:29:17 UTC
- Source modified
- 4 Feb 2026 02:59:23 UTC
- Saved here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.