GHSA-5367-6MXW-83V4
Vulnerability from github – Published: 2026-09-11 21:31 – Updated: 2026-09-13 09:32In the Linux kernel, the following vulnerability has been resolved:
sysctl: move the "cad_pid" entry from pid_table[] to kern_reboot_table[]
cad_pid is global, and kill_cad_pid() is only used in the root namespace.
However, due to pid_table_root_permissions(), a non-root user can unshare pid/user namespaces and modify it from the child namespace. This makes no sense and is simply wrong.
Move it to kern_reboot_table[] where it logically belongs; this ensures that only GLOBAL_ROOT_UID can read/modify this sysctl.
Note that this patch doesn't preserve "#ifdef CONFIG_PROC_SYSCTL" around the "cad_pid"; CONFIG_PROC_SYSCTL selects CONFIG_SYSCTL, so it is always set when kern_reboot_table[] is compiled.
{
"affected": [],
"aliases": [
"CVE-2026-80929"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-11T20:18:56Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nsysctl: move the \"cad_pid\" entry from pid_table[] to kern_reboot_table[]\n\ncad_pid is global, and kill_cad_pid() is only used in the root namespace.\n\nHowever, due to pid_table_root_permissions(), a non-root user can unshare\npid/user namespaces and modify it from the child namespace. This makes no\nsense and is simply wrong.\n\nMove it to kern_reboot_table[] where it logically belongs; this ensures\nthat only GLOBAL_ROOT_UID can read/modify this sysctl.\n\nNote that this patch doesn\u0027t preserve \"#ifdef CONFIG_PROC_SYSCTL\" around\nthe \"cad_pid\"; CONFIG_PROC_SYSCTL selects CONFIG_SYSCTL, so it is always\nset when kern_reboot_table[] is compiled.",
"id": "GHSA-5367-6mxw-83v4",
"modified": "2026-09-13T09:32:08Z",
"published": "2026-09-11T21:31:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-80929"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7170ca01623b399c97f2ae9d3e228badc1f25ea3"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a09bc4eaa67e1a72df3b6d0beb3afeef1e1fdfcd"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e8527de7fea191fda704792a56081f9009aeec37"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.