CVE-2026-64111 (CVSS 7.1)

Description

In the Linux kernel, the following vulnerability has been resolved: lsm: hold cred_guard_mutex for lsm_set_self_attr() Just as proc_pid_attr_write() already does before calling the LSM hook. This only matters for SELinux and AppArmor which check whether the process is being ptraced and if so, whether to allow the transition.

Is your site exposed to CVE-2026-64111?

Run a free security scan — no signup, results in seconds.

CVSS v3.1 Score

7.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

EPSS — Exploit Prediction

0.0014

Probability of exploitation

0.03%

Percentile rank

EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.

References

Other References

https://git.kernel.org/stable/c/4a9b16541ad3faf8bccb398532bf3f8b6bbf1188 https://git.kernel.org/stable/c/5b906f31e977286888a9e31282589b545b249139 https://git.kernel.org/stable/c/82d3acee88593e3d9e71cad4b7d6b3cf70de9d07 https://git.kernel.org/stable/c/a010cadaf5727b8417f62fe9021fcef14a5f9b51

Frequently Asked Questions

What is CVE-2026-64111? +

In the Linux kernel, the following vulnerability has been resolved: lsm: hold cred_guard_mutex for lsm_set_self_attr() Just as proc_pid_attr_write() already does before calling the LSM hook. This only matters for SELinux and AppArmor which check whether the process is being ptraced and if so, whether to allow the transition. It has a CVSS v3.1 base score of 7.1 (HIGH).

How severe is CVE-2026-64111? +

CVE-2026-64111 has a CVSS v3.1 score of 7.1 out of 10, rated HIGH. This is a high-severity vulnerability that should be prioritized for patching. The EPSS score is 0.0014, placing it in the 0th percentile for exploitation probability.

How do I check if I'm vulnerable to CVE-2026-64111? +

You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.

CVE-2026-64111