CVE-2026-72460 — apparmor: check label build before no_new_privs test
In the Linux kernel, the following vulnerability has been resolved: apparmor: check label build before no_new_privs test aa_change_profile() builds a replacement label with fn_label_build_in_scope() before the no_new_privs subset check. The build helper can fail and return NULL or an ERR_PTR, but the result was passed to aa_label_is_unconfined_subset() before the existing IS_ERR_OR_NULL() check. Reuse the existing target-label build failure handling immediately after the build. This preserves the current audit handling while preventing the subset helper from dereferencing an invalid label.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ e00b02bb6ac2a1893227ce8014b649028d6425d2 and < a29f06db44b4c94597ded58f639eed3e21781ac3≥ e00b02bb6ac2a1893227ce8014b649028d6425d2 and < cfc224866530a6842b6c2d2d30ef6a9b0e64bb9c≥ e00b02bb6ac2a1893227ce8014b649028d6425d2 and < 31cb109db5e6322ed22304fd5c0dedbaa438d6d3≥ e00b02bb6ac2a1893227ce8014b649028d6425d2 and < b7c45c05a396a017c49ac7949de240a0dfc0ac4e≥ e00b02bb6ac2a1893227ce8014b649028d6425d2 and < d84bb195d208adbf77f012ca2a96e11163f6def1≥ e00b02bb6ac2a1893227ce8014b649028d6425d2 and < d82160132345688a09cbaa648cfdd16bb32e8ea2≥ e00b02bb6ac2a1893227ce8014b649028d6425d2 and < ec926b2a351eeeb31e6c9aee02e0c32f94b5588f≥ e00b02bb6ac2a1893227ce8014b649028d6425d2 and < a58cafd38b46fb1a2220e2fbbcfe291ea75fa147 and 1 moreversion 4.13 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.1 | CVSS 3.1 | High | 1.8 | 5.2 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.1 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- CVSS changed · 7.1
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/d84bb195d208adbf77f012ca2a96e11163f6def1
- git.kernel.org/stable/c/d82160132345688a09cbaa648cfdd16bb32e8ea2
- git.kernel.org/stable/c/cfc224866530a6842b6c2d2d30ef6a9b0e64bb9c
- git.kernel.org/stable/c/a29f06db44b4c94597ded58f639eed3e21781ac3
- git.kernel.org/stable/c/31cb109db5e6322ed22304fd5c0dedbaa438d6d3
- git.kernel.org/stable/c/ec926b2a351eeeb31e6c9aee02e0c32f94b5588f
- git.kernel.org/stable/c/a58cafd38b46fb1a2220e2fbbcfe291ea75fa147
- git.kernel.org/stable/c/b7c45c05a396a017c49ac7949de240a0dfc0ac4e
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 16h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 16h
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-72460 is "apparmor: check label build before no_new_privs test", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.1 describes technical severity. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.