Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-72459: apparmor: aa_label_alloc use aa_label_free on alloc failure

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/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.13% (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 654fe7505dc6889724d4094fa64f89991afabfc3, 6d91479174240f39e9edea250d95fa08c678a207, 7cb69e109610bba500e1ecb870f7988a4717208a.

Low priority for now. Upgrade to Linux Linux 654fe7505dc6889724d4094fa64f89991afabfc3, 6d91479174240f39e9edea250d95fa08c678a207, 7cb69e109610bba500e1ecb870f7988a4717208a 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: aa_label_alloc use aa_label_free on alloc failure aa_label_alloc() allocates a secid before allocating or taking the label proxy. If the later proxy step fails, the error path only freed the label memory, leaking any resources initialized by aa_label_init(). Use aa_label_free() on the failure path so partially initialized labels release their secid and other label resources before the backing memory is freed.

Published
Aug 15, 2026
Updated
Aug 17, 2026
EPSS
0.1% · 3th percentile
CWE
—

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CNA vs NVD score

NVD
—
CNA · Linux
7.8
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-72459

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
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
    • f1bd904175e8190ce14aedee37e207ab51fe3b30 and later · before b14fbacad77d64594228983ec20d61a224f3f491affected · git
    • f1bd904175e8190ce14aedee37e207ab51fe3b30 and later · before b5a9da5d36162d34db0f36abb15420e295176793affected · git
    • f1bd904175e8190ce14aedee37e207ab51fe3b30 and later · before 7cb69e109610bba500e1ecb870f7988a4717208aaffected · git
    • f1bd904175e8190ce14aedee37e207ab51fe3b30 and later · before cc2192899d502e3321e60cf1e91421e7309d089caffected · git
    • f1bd904175e8190ce14aedee37e207ab51fe3b30 and later · before bf310b044e85d4de670c94295c5d8e4c5bc5e7bcaffected · git
    • f1bd904175e8190ce14aedee37e207ab51fe3b30 and later · before ae02e603c0b39b29f3ce6fe3efe01b286af1a2a4affected · git
    • f1bd904175e8190ce14aedee37e207ab51fe3b30 and later · before 6d91479174240f39e9edea250d95fa08c678a207affected · git
    • f1bd904175e8190ce14aedee37e207ab51fe3b30 and later · before 654fe7505dc6889724d4094fa64f89991afabfc3affected · 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

Same product

linux: all records

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-72457Aug 15, 2026 · apparmor: fail policy unpack on accept2 allocation failure
    0Monitor
  • ← EarlierCVE-2026-72458Aug 15, 2026 · apparmor: fix NULL pointer dereference in unpack_pdb
    0Monitor
  • Later →CVE-2026-72460Aug 15, 2026 · apparmor: check label build before no_new_privs test
    28Monitor

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 Linux654fe7505dc6889724d4094fa64f89991afabfc3Vendor (CNA)
Linux Linux6d91479174240f39e9edea250d95fa08c678a207Vendor (CNA)
Linux Linux7cb69e109610bba500e1ecb870f7988a4717208aVendor (CNA)
Linux Linuxae02e603c0b39b29f3ce6fe3efe01b286af1a2a4Vendor (CNA)
Linux Linuxb14fbacad77d64594228983ec20d61a224f3f491Vendor (CNA)
Linux Linuxb5a9da5d36162d34db0f36abb15420e295176793Vendor (CNA)
Linux Linuxbf310b044e85d4de670c94295c5d8e4c5bc5e7bcVendor (CNA)
Linux Linuxcc2192899d502e3321e60cf1e91421e7309d089cVendor (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
high · data or configuration can be modified
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
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records