CVE-2026-72460: apparmor: check label build before no_new_privs test
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 31cb109db5e6322ed22304fd5c0dedbaa438d6d3, a29f06db44b4c94597ded58f639eed3e21781ac3, a58cafd38b46fb1a2220e2fbbcfe291ea75fa147.
Low priority for now. Upgrade to Linux Linux 31cb109db5e6322ed22304fd5c0dedbaa438d6d3, a29f06db44b4c94597ded58f639eed3e21781ac3, a58cafd38b46fb1a2220e2fbbcfe291ea75fa147 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 15, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.1
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.13affected
- e00b02bb6ac2a1893227ce8014b649028d6425d2 and later · before a29f06db44b4c94597ded58f639eed3e21781ac3affected · git
- e00b02bb6ac2a1893227ce8014b649028d6425d2 and later · before cfc224866530a6842b6c2d2d30ef6a9b0e64bb9caffected · git
- e00b02bb6ac2a1893227ce8014b649028d6425d2 and later · before 31cb109db5e6322ed22304fd5c0dedbaa438d6d3affected · git
- e00b02bb6ac2a1893227ce8014b649028d6425d2 and later · before b7c45c05a396a017c49ac7949de240a0dfc0ac4eaffected · git
- e00b02bb6ac2a1893227ce8014b649028d6425d2 and later · before d84bb195d208adbf77f012ca2a96e11163f6def1affected · git
- e00b02bb6ac2a1893227ce8014b649028d6425d2 and later · before d82160132345688a09cbaa648cfdd16bb32e8ea2affected · git
- e00b02bb6ac2a1893227ce8014b649028d6425d2 and later · before ec926b2a351eeeb31e6c9aee02e0c32f94b5588faffected · git
- e00b02bb6ac2a1893227ce8014b649028d6425d2 and later · before a58cafd38b46fb1a2220e2fbbcfe291ea75fa147affected · git
- before 4.13not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72458Aug 15, 2026 · apparmor: fix NULL pointer dereference in unpack_pdb0Monitor
- ← EarlierCVE-2026-72459Aug 15, 2026 · apparmor: aa_label_alloc use aa_label_free on alloc failure31Monitor
- Later →CVE-2026-72461Aug 15, 2026 · apparmor: fix refcount leak when updating the sk_ctx31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 31cb109db5e6322ed22304fd5c0dedbaa438d6d3 | Vendor (CNA) |
| Linux Linux | a29f06db44b4c94597ded58f639eed3e21781ac3 | Vendor (CNA) |
| Linux Linux | a58cafd38b46fb1a2220e2fbbcfe291ea75fa147 | Vendor (CNA) |
| Linux Linux | b7c45c05a396a017c49ac7949de240a0dfc0ac4e | Vendor (CNA) |
| Linux Linux | cfc224866530a6842b6c2d2d30ef6a9b0e64bb9c | Vendor (CNA) |
| Linux Linux | d82160132345688a09cbaa648cfdd16bb32e8ea2 | Vendor (CNA) |
| Linux Linux | d84bb195d208adbf77f012ca2a96e11163f6def1 | Vendor (CNA) |
| Linux Linux | ec926b2a351eeeb31e6c9aee02e0c32f94b5588f | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/a29f06db44b4c94597ded58f639eed3e21781ac3
- git.kernel.org/stable/c/a58cafd38b46fb1a2220e2fbbcfe291ea75fa147
- git.kernel.org/stable/c/b7c45c05a396a017c49ac7949de240a0dfc0ac4e
- git.kernel.org/stable/c/cfc224866530a6842b6c2d2d30ef6a9b0e64bb9c
- git.kernel.org/stable/c/d82160132345688a09cbaa648cfdd16bb32e8ea2
- git.kernel.org/stable/c/d84bb195d208adbf77f012ca2a96e11163f6def1
- git.kernel.org/stable/c/ec926b2a351eeeb31e6c9aee02e0c32f94b5588f
Vendor advisories and official records. Exploit/PoC links are deliberately left out.