Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-72460: apparmor: check label build before no_new_privs test

HighCVSS 7.1 · v3.1—No exploit Fix available

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

JSON

Action score

28

Monitor

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.

Follow CVE-2026-72460

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

Noroxi 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 help

Affected 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.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.5-17.1.5-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • 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_pdb
    0Monitor
  • ← EarlierCVE-2026-72459Aug 15, 2026 · apparmor: aa_label_alloc use aa_label_free on alloc failure
    31Monitor
  • Later →CVE-2026-72461Aug 15, 2026 · apparmor: fix refcount leak when updating the sk_ctx
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux31cb109db5e6322ed22304fd5c0dedbaa438d6d3Vendor (CNA)
Linux Linuxa29f06db44b4c94597ded58f639eed3e21781ac3Vendor (CNA)
Linux Linuxa58cafd38b46fb1a2220e2fbbcfe291ea75fa147Vendor (CNA)
Linux Linuxb7c45c05a396a017c49ac7949de240a0dfc0ac4eVendor (CNA)
Linux Linuxcfc224866530a6842b6c2d2d30ef6a9b0e64bb9cVendor (CNA)
Linux Linuxd82160132345688a09cbaa648cfdd16bb32e8ea2Vendor (CNA)
Linux Linuxd84bb195d208adbf77f012ca2a96e11163f6def1Vendor (CNA)
Linux Linuxec926b2a351eeeb31e6c9aee02e0c32f94b5588fVendor (CNA)
debian:linux6.1.180-1 · Debian:12Package 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.

EPSS, last 120 days

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.

References

All records