CVE-2026-90246

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. A secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.1Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

In the Linux kernel, the following vulnerability has been resolved:

apparmor: fix integer overflow in verify_tags() bounds check

verify_tags() validates the tagset table unpacked from a policy blob. For each set it reads a count and checks that advancing the index by that count stays inside sets.table[]:

u32 cnt = tags->sets.table[i];

if (i+cnt >= tags->sets.size) {

i, cnt and sets.size are all u32, so i+cnt is evaluated modulo 2^32. sets.table[] is filled by unpack_tagsets() with aa_unpack_u32(), so every entry is a raw unbounded 32-bit word taken from the policy blob, and verify_tags() is the function that is supposed to validate it. A count close to U32_MAX makes the sum wrap to a small value, the guard passes, and the inner loop then walks sets.table[++i] past the end of the kcalloc(size, sizeof(u32)) allocation.

Note that sets.size is bounded by 65535, because unpack_tagsets() reads it with aa_unpack_array() as a u16, so the wrap cannot be reached by growing the table; it is reached purely through the attacker-supplied count.

With sets.size = 2 and sets.table = { 0, 0xffffffff }:

i = 0: cnt = 0, guard 0 + 0 >= 2 is false, inner loop does not run i = 1: cnt = 0xffffffff, guard (1 + 0xffffffff) mod 2^32 == 0 >= 2 is false, so the guard is bypassed and the inner loop reads sets.table[2] -- one element past a two element allocation

The walk continues until an out-of-bounds value happens to be >= hdrs.size or the access faults, so a crafted policy yields an out-of-bounds read on the policy load path (aa_replace_profiles -> aa_unpack -> unpack_policydb -> unpack_tags -> verify_tags). unpack_tags() runs before the perms and DFA tables are unpacked, so no other table needs to be well formed to reach it.

Policy load is gated by aa_may_manage_policy(), which checks CAP_MAC_ADMIN relative to the subject's own user namespace rather than the init user namespace, so with the default unprivileged_userns_apparmor_policy=1 the path is reachable from an unprivileged task in a matched-level nested namespace, not only by a globally privileged one.

Perform the addition in u64 so that it cannot wrap, restoring the intended i + cnt < sets.size guarantee.

CVSS v3
7.1
EG Score
7.1HIGHhigh confidence
EG Risk
37
EG Risk 37/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (2)

Auto-updated Sep 18, 2026
No patch confirmed yet.
generic

apparmor: fix integer overflow in verify_tags() bounds check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ef79a405f83993f0fda5efde371d98433f7d7a47
generic

apparmor: fix integer overflow in verify_tags() bounds check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/465946d3c560c0137e6a180ba054dddc4d049f5a

Vendor Advisories for CVE-2026-90246(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (178 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 26× in last 7d / 70× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 07:41 UTCEG score recompute
  2. 2026-10-05 07:41 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 19:01 UTCGHSA enrichment
  5. 2026-10-04 06:03 UTCGHSA enrichment
  6. 2026-10-03 17:24 UTCEG score recompute
  7. 2026-10-03 17:24 UTCGHSA enrichment
  8. 2026-10-03 04:45 UTCEG score recompute
  9. 2026-10-03 04:45 UTCGHSA enrichment
  10. 2026-10-02 16:05 UTCGHSA enrichment
  11. 2026-10-02 03:25 UTCEG score recompute
  12. 2026-10-02 03:25 UTCGHSA enrichment
  13. 2026-10-01 19:51 UTCEPSS rescore
  14. 2026-10-01 14:46 UTCGHSA enrichment
  15. 2026-10-01 02:06 UTCEG score recompute
  16. 2026-10-01 02:06 UTCGHSA enrichment
  17. 2026-09-30 15:04 UTCEPSS rescore
  18. 2026-09-30 13:26 UTCGHSA enrichment
  19. 2026-09-30 00:44 UTCEG score recompute
  20. 2026-09-30 00:44 UTCGHSA enrichment
  21. 2026-09-29 08:17 UTCEG score recompute
  22. 2026-09-29 08:17 UTCGHSA enrichment
  23. 2026-09-28 19:38 UTCEG score recompute
  24. 2026-09-28 19:38 UTCGHSA enrichment
  25. 2026-09-28 13:52 UTCEPSS rescore
Show 45 more
  1. 2026-09-28 13:52 UTCEPSS rescore
  2. 2026-09-28 06:35 UTCGHSA enrichment
  3. 2026-09-27 17:55 UTCEG score recompute
  4. 2026-09-27 17:55 UTCGHSA enrichment
  5. 2026-09-27 13:49 UTCEPSS rescore
  6. 2026-09-27 05:15 UTCGHSA enrichment
  7. 2026-09-26 16:35 UTCEG score recompute
  8. 2026-09-26 16:35 UTCGHSA enrichment
  9. 2026-09-26 15:59 UTCEPSS rescore
  10. 2026-09-26 03:52 UTCEG score recompute
  11. 2026-09-26 03:52 UTCGHSA enrichment
  12. 2026-09-25 15:06 UTCGHSA enrichment
  13. 2026-09-25 02:25 UTCEG score recompute
  14. 2026-09-25 02:25 UTCGHSA enrichment
  15. 2026-09-24 14:04 UTCEPSS rescore
  16. 2026-09-24 13:45 UTCGHSA enrichment
  17. 2026-09-24 01:05 UTCEG score recompute
  18. 2026-09-24 01:05 UTCGHSA enrichment
  19. 2026-09-23 17:54 UTCEPSS rescore
  20. 2026-09-23 12:26 UTCGHSA enrichment
  21. 2026-09-22 23:47 UTCEG score recompute
  22. 2026-09-22 23:47 UTCGHSA enrichment
  23. 2026-09-22 16:01 UTCEPSS rescore
  24. 2026-09-22 11:07 UTCGHSA enrichment
  25. 2026-09-21 22:27 UTCEG score recompute
  26. 2026-09-21 22:27 UTCGHSA enrichment
  27. 2026-09-21 21:09 UTCEPSS rescore
  28. 2026-09-21 09:48 UTCGHSA enrichment
  29. 2026-09-20 21:08 UTCEG score recompute
  30. 2026-09-20 21:08 UTCGHSA enrichment
  31. 2026-09-20 20:16 UTCEPSS rescore
  32. 2026-09-20 08:29 UTCGHSA enrichment
  33. 2026-09-19 19:49 UTCEG score recompute
  34. 2026-09-19 19:49 UTCGHSA enrichment
  35. 2026-09-19 07:10 UTCEG score recompute
  36. 2026-09-19 07:10 UTCGHSA enrichment
  37. 2026-09-18 19:28 UTCEPSS rescore
  38. 2026-09-18 18:30 UTCEG score recompute
  39. 2026-09-18 18:30 UTCGHSA enrichment
  40. 2026-09-18 18:03 UTCEG score recompute▲ 7.10
  41. 2026-09-18 18:03 UTCGHSA enrichment
  42. 2026-09-18 17:59 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  43. 2026-09-17 17:24 UTCNVD update
  44. 2026-09-17 16:37 UTCEG score recompute
  45. 2026-09-17 16:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-90246?
CVE-2026-90246 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: apparmor: fix integer overflow in verify_tags() bounds check verify_tags() validates the tagset table unpacked from a policy blob. For each set it reads a count and checks that advancing the index by that count stays inside…
When was CVE-2026-90246 disclosed?
CVE-2026-90246 was first published on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90246 actively exploited?
CVE-2026-90246 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90246?
CVE-2026-90246 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-90246?
No fix for CVE-2026-90246 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-90246 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-90246

Explore →

Is Your Infrastructure Affected by CVE-2026-90246?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.