Bug 2404705 (CVE-2025-31133) - CVE-2025-31133 runc: container escape via 'masked path' abuse due to mount race conditions
Summary: CVE-2025-31133 runc: container escape via 'masked path' abuse due to mount ra...
Keywords:
Status: NEW
Alias: CVE-2025-31133
Deadline: 2025-11-05
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2412995 2412996
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-10-17 14:42 UTC by OSIDB Bzimport
Modified: 2026-01-07 07:15 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2025:19927 0 None None None 2025-11-07 18:01:00 UTC
Red Hat Product Errata RHSA-2025:20957 0 None None None 2025-11-11 15:00:12 UTC
Red Hat Product Errata RHSA-2025:21232 0 None None None 2025-11-13 10:36:07 UTC
Red Hat Product Errata RHSA-2025:21328 0 None None None 2025-11-20 07:48:45 UTC
Red Hat Product Errata RHSA-2025:21795 0 None None None 2025-11-27 04:22:37 UTC
Red Hat Product Errata RHSA-2025:21824 0 None None None 2025-11-27 11:07:14 UTC
Red Hat Product Errata RHSA-2025:22275 0 None None None 2025-12-05 13:27:10 UTC
Red Hat Product Errata RHSA-2025:23113 0 None None None 2026-01-07 07:15:25 UTC

Description OSIDB Bzimport 2025-10-17 14:42:43 UTC 
A flaw was found in runc. This flaw exploits an issue with how masked paths are implementedin runc. When masking files, runc will bind-mount the container's /dev/null inode on top of the file. However, if an attacker can replace /dev/null with a symlink to some other procfs file, runc will instead bind-mount the symlink target read-write.
Comment 1 errata-xmlrpc 2025-11-07 18:00:59 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2025:19927 https://access.redhat.com/errata/RHSA-2025:19927
Comment 2 errata-xmlrpc 2025-11-11 15:00:11 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2025:20957 https://access.redhat.com/errata/RHSA-2025:20957
Comment 3 errata-xmlrpc 2025-11-13 10:36:06 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2025:21232 https://access.redhat.com/errata/RHSA-2025:21232
Comment 4 errata-xmlrpc 2025-11-20 07:48:44 UTC 
This issue has been addressed in the following products:

  Red Hat OpenShift Container Platform 4.14

Via RHSA-2025:21328 https://access.redhat.com/errata/RHSA-2025:21328
Comment 5 errata-xmlrpc 2025-11-27 04:22:36 UTC 
This issue has been addressed in the following products:

  Red Hat OpenShift Container Platform 4.18

Via RHSA-2025:21795 https://access.redhat.com/errata/RHSA-2025:21795
Comment 6 errata-xmlrpc 2025-11-27 11:07:12 UTC 
This issue has been addressed in the following products:

  Red Hat OpenShift Container Platform 4.16

Via RHSA-2025:21824 https://access.redhat.com/errata/RHSA-2025:21824
Comment 7 errata-xmlrpc 2025-12-05 13:27:09 UTC 
This issue has been addressed in the following products:

  Red Hat OpenShift Container Platform 4.13

Via RHSA-2025:22275 https://access.redhat.com/errata/RHSA-2025:22275
Comment 8 errata-xmlrpc 2026-01-07 07:15:24 UTC 
This issue has been addressed in the following products:

  Red Hat OpenShift Container Platform 4.15

Via RHSA-2025:23113 https://access.redhat.com/errata/RHSA-2025:23113
Note You need to log in before you can comment on or make changes to this bug.