How many CVEs have patched ProcThreadSelfOpen?

1 published CVEs changed ProcThreadSelfOpen in opencontainers/runc, in 1 distinct patches totalling 6 changed lines, between 2025 and 2025.

What is the latest CVE that changed ProcThreadSelfOpen?

CVE-2025-52881 (runc: LSM labels can be bypassed with malicious config using dummy procfs files), published 2025-11-06, changed lines 75 to 83 of internal/pathrs/procfs_pathrslite.go.

How does ProcThreadSelfOpen compare to the rest of opencontainers/runc?

opencontainers/runc has 16 CVEs with a located fix in total; 1 of them changed ProcThreadSelfOpen.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

opencontainers/runc

Function

ProcThreadSelfOpen

Name: ProcThreadSelfOpen in opencontainers/runc: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

internal/pathrs/procfs_pathrslite.go

Last patched November 6, 2025

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

6

Lines changed

Added plus removed

2025

Years

By CVE publication date

Overview

ProcThreadSelfOpen in opencontainers/runc was changed by 1 published CVE fixes in 2025, in 1 distinct patches that added or removed 6 lines in total.

opencontainers/runc has 16 CVEs with a located fix in total, so 6% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed ProcThreadSelfOpen, newest first, with the lines each fix touched.

runc: LSM labels can be bypassed with malicious config using dummy procfs files
CVE-2025-52881 · lines 75–83 · +4 −2
High · CVSS 7.3
EPSS 0.6%2025-11-06

Get an alert when the next CVE fix lands in opencontainers/runc, with the patched functions.

Monitor runc CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in opencontainers/runc changed by the most CVE fixes.

mountToRootfs6 CVEs · libcontainer/rootfs_linux.go mountCgroupV25 CVEs · libcontainer/rootfs_linux.go Init5 CVEs · libcontainer/standard_init_linux.go createDeviceNode4 CVEs · libcontainer/rootfs_linux.go mountCgroupV13 CVEs · libcontainer/rootfs_linux.go Close3 CVEs · libcontainer/rootfs_linux.go

All patched functions in opencontainers/runc

Frequently asked questions

Common questions about CVE fixes to ProcThreadSelfOpen.

How many CVEs have patched ProcThreadSelfOpen?: 1 published CVEs changed ProcThreadSelfOpen in opencontainers/runc, in 1 distinct patches totalling 6 changed lines, between 2025 and 2025.
What is the latest CVE that changed ProcThreadSelfOpen?: CVE-2025-52881 (runc: LSM labels can be bypassed with malicious config using dummy procfs files), published 2025-11-06, changed lines 75 to 83 of internal/pathrs/procfs_pathrslite.go.
How does ProcThreadSelfOpen compare to the rest of opencontainers/runc?: opencontainers/runc has 16 CVEs with a located fix in total; 1 of them changed ProcThreadSelfOpen.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track opencontainers/runc CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing