HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members
  • Sponsor HOL
  • Advertise with HOL

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorFund agreed research, implementation and shared testing through the HOL Partner Program.
  • AdvertiseCompare README logo placements, previews and monthly prices, or promote a plugin or extension.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 90179 apparmor fix deadlock in complain mode changehat
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Telegram
  • X
More
  • About HOL
  • Sponsor
  • Advertise
  • Affiliate program
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
Unknown severity · Source severity not reportedCVE-2026-90179

apparmor: fix deadlock in complain-mode change_hatCVE-2026-90179

Answer in brief

CVE-2026-90179 records a Unknown severity vulnerability in apparmor: fix deadlock in complain-mode change_hat. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 17, 2026Updated Oct 30, 2026Source checked Nov 1, 2026First seen by HOL Sep 17, 2026Material review Oct 30, 2026
Upstream Advisory

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
Not reported
Source
CVE List V5
Source checked
Nov 1, 2026
References
6 linked sources
Open source record

Key facts

Risk
Unknown severitySource severity not reported
Exploitation
Not marked as known exploited
Affected software
4 mapped packages or products
Fix availability
Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=b427061ca498309bf581bb6f8df4ffcfe4c772cd <00cce5e457cb690a3b3b3d334e76e71049ec8ae5 || >=32e92764d6f8d251c1bca62be33793287b453a81 <072fb5aeec2eac7d445bf28c7119a1d6f6a2e333 || >=32e92764d6f8d251c1bca62be33793287b453a81 <4ec11f14d1d6fdda787d991b142537be7841d395 || 862ae1fcc78aea9acab2ac87cccf6431f4682b8e || 65f95c1e7ce70bf339504e22473879e02026cfc4 || 9735e300a1c9259bfe4dc5ecdba472bb25574e8a || 5acb878db41328dae4d3249bc87b9ee4f290a663 || 6446dbe02f4a3592bf062b4d12105927993086af || 67ee65ec1a3eebdde76ccaa664d20dcf5b125a2f || >=6.18.40 <6.18.52 || >=5.10.261 <5.11 || >=5.15.212 <5.16 || >=6.1.178 <6.2 || >=6.6.145 <6.7 || >=6.12.97 <6.13 || >=7.1.5 <7.200cce5e457cb690a3b3b3d334e76e71049ec8ae5, 072fb5aeec2eac7d445bf28c7119a1d6f6a2e333, 4ec11f14d1d6fdda787d991b142537be7841d395, 6.18.52, 5.11, 5.16, 6.2, 6.7, 6.13, 7.2
Linux/Linuxgeneric7.2Not reported
Linux/Linuxgeneric>=5acb878db41328dae4d3249bc87b9ee4f290a663 <5f1fedccf3f7add5e2a1205ac4938fa3893c5874 || >=6446dbe02f4a3592bf062b4d12105927993086af <91fce09d89b2d397996226216820f0e8b8149e22 || >=b427061ca498309bf581bb6f8df4ffcfe4c772cd <00cce5e457cb690a3b3b3d334e76e71049ec8ae5 || >=32e92764d6f8d251c1bca62be33793287b453a81 <072fb5aeec2eac7d445bf28c7119a1d6f6a2e333 || >=32e92764d6f8d251c1bca62be33793287b453a81 <4ec11f14d1d6fdda787d991b142537be7841d395 || 862ae1fcc78aea9acab2ac87cccf6431f4682b8e || 65f95c1e7ce70bf339504e22473879e02026cfc4 || 9735e300a1c9259bfe4dc5ecdba472bb25574e8a || 67ee65ec1a3eebdde76ccaa664d20dcf5b125a2f || >=6.6.145 <6.6.160 || >=6.12.97 <6.12.114 || >=6.18.40 <6.18.52 || >=5.10.261 <5.11 || >=5.15.212 <5.16 || >=6.1.178 <6.2 || >=7.1.5 <7.25f1fedccf3f7add5e2a1205ac4938fa3893c5874, 91fce09d89b2d397996226216820f0e8b8149e22, 00cce5e457cb690a3b3b3d334e76e71049ec8ae5, 072fb5aeec2eac7d445bf28c7119a1d6f6a2e333, 4ec11f14d1d6fdda787d991b142537be7841d395, 6.6.160, 6.12.114, 6.18.52, 5.11, 5.16, 6.2, 7.2
Linux/Linuxgeneric>=9735e300a1c9259bfe4dc5ecdba472bb25574e8a <fb8ac089815dc192d891294cf0ffeeafd910136a || >=5acb878db41328dae4d3249bc87b9ee4f290a663 <5f1fedccf3f7add5e2a1205ac4938fa3893c5874 || >=6446dbe02f4a3592bf062b4d12105927993086af <91fce09d89b2d397996226216820f0e8b8149e22 || >=b427061ca498309bf581bb6f8df4ffcfe4c772cd <00cce5e457cb690a3b3b3d334e76e71049ec8ae5 || >=32e92764d6f8d251c1bca62be33793287b453a81 <072fb5aeec2eac7d445bf28c7119a1d6f6a2e333 || >=32e92764d6f8d251c1bca62be33793287b453a81 <4ec11f14d1d6fdda787d991b142537be7841d395 || 862ae1fcc78aea9acab2ac87cccf6431f4682b8e || 65f95c1e7ce70bf339504e22473879e02026cfc4 || 67ee65ec1a3eebdde76ccaa664d20dcf5b125a2f || >=6.1.178 <6.1.191 || >=6.6.145 <6.6.160 || >=6.12.97 <6.12.114 || >=6.18.40 <6.18.52 || >=5.10.261 <5.11 || >=5.15.212 <5.16 || >=7.1.5 <7.2fb8ac089815dc192d891294cf0ffeeafd910136a, 5f1fedccf3f7add5e2a1205ac4938fa3893c5874, 91fce09d89b2d397996226216820f0e8b8149e22, 00cce5e457cb690a3b3b3d334e76e71049ec8ae5, 072fb5aeec2eac7d445bf28c7119a1d6f6a2e333, 4ec11f14d1d6fdda787d991b142537be7841d395, 6.1.191, 6.6.160, 6.12.114, 6.18.52, 5.11, 5.16, 7.2

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux, Linux/Linux.
  2. 2Review the reported fix. Update Linux/Linux to 00cce5e457cb690a3b3b3d334e76e71049ec8ae5; Linux/Linux to 5f1fedccf3f7add5e2a1205ac4938fa3893c5874; Linux/Linux to fb8ac089815dc192d891294cf0ffeeafd910136a if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Sep 17, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  2. Source modified

    Oct 30, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  3. First seen by HOL

    Sep 17, 2026

Sources and claim methodology

  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
Upstream source description

In the Linux kernel, the following vulnerability has been resolved: apparmor: fix deadlock in complain-mode change_hat The use of change_hat when in complain mode can cause a deadlock when the hat doesn't exist and a new learning profile is created for the missing profile. This is because change_hat() has taken the lock to search the hat list and creating the new learning profile needs to take the lock to add it to the list. From the bug report: Originally found in 7.0.0 in LTS ubuntu 26.04 with pam_apparmor + su in complain mode set to change hats. Then verified in newest available vanilla kernel I've compiled to see if still present: 7.2-rc7 vanilla -> affected checked also some other kernels: 6.18.44 vanilla -> affected 6.12.95 with debian patches -> unaffected On systems without bug (for example 6.12.95 debian) it just prints: aa_change_hat rc=0 On systems with bug, the executable always hangs, prints nothing and becomes unkillable. (And once stuck this way, it will cause any further hat changes to also cause the changing process to get stuck) Then in syslog you can find hint about cause: kernel: INFO: task hat:3409 blocked for more than 483 seconds. kernel: Not tainted 7.2.0-rc7 #1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. kernel: task:hat state:D stack:0 pid:3409 tgid:3409 ppid:2605 task_flags:0x400000 flags:0x00080800 kernel: Call Trace: kernel: <TASK> kernel: __schedule+0x48f/0xfe0 kernel: schedule+0x27/0xa0 kernel: schedule_preempt_disabled+0x15/0x30 kernel: __mutex_lock.constprop.0+0x569/0xa10 kernel: aa_new_learning_profile+0x15f/0x210 kernel: build_change_hat+0x19f/0x3b0 kernel: change_hat.isra.0+0x5dd/0xd60 kernel: aa_change_hat+0x2f3/0x710 kernel: aa_setprocattr_changehat+0x121/0x1f0 kernel: do_setattr+0x28c/0x340 kernel: apparmor_setselfattr+0x20/0x50 kernel: security_setselfattr+0xf6/0x110 kernel: __x64_sys_lsm_set_self_attr+0x53/0x90 kernel: do_syscall_64+0xdd/0x5e0 kernel: ? __mod_memcg_lruvec_state+0xfd/0x260 kernel: ? lruvec_stat_mod_folio+0x8d/0xd0 kernel: ? __folio_mod_stat+0x2d/0x90 kernel: ? map_anon_folio_pte_nopf+0xd1/0x1f0 kernel: ? do_anonymous_page+0x184/0xa10 kernel: ? __handle_mm_fault+0x805/0x870 kernel: ? count_memcg_events+0xef/0x230 kernel: ? handle_mm_fault+0x1f0/0x2f0 kernel: ? do_user_addr_fault+0x2bb/0x7b0 kernel: ? do_syscall_64+0x94/0x5e0 kernel: ? exc_page_fault+0x75/0x160 kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e kernel: RIP: 0033:0x7f815e134c8d kernel: RSP: 002b:00007fff6df94ea8 EFLAGS: 00000246 ORIG_RAX: 00000000000001cc kernel: RAX: ffffffffffffffda RBX: 0000556d8c81d040 RCX: 00007f815e134c8d kernel: RDX: 0000000000000046 RSI: 0000556d8c81d040 RDI: 0000000000000064 kernel: RBP: 00007fff6df94ef0 R08: 00007f815e212ac8 R09: 000000000000000c kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000556d8c81d010 kernel: R13: 0000000000000026 R14: 0000000000000046 R15: 0000000000000064 kernel: </TASK> kernel: INFO: task hat:3409 is blocked on a mutex likely owned by task hat:3409. To fix the issue, lift the locking out of the core of aa_new_learning_profile(), introduce a wrapper function that takes the lock where needed, and have build_change_hat() call the core function that no longer takes the lock. In addition fix 4 other issues introduced by commit 32e92764d6f8d ("apparmor: grab ns lock and refresh when looking up changehat child profiles") - aa_get_profile_rcu() was replaced-by: aa_get_profile without the accompanying rcu_dereference_protected() - an extra aa_get_label(label) was introduced at the start of change_hat() without an accompanying aa_put_label() causing a reference count leak. - a reference count leak was introduced in the label_is_stale(label) case, where the newest profile would be leaked instead of the label passed to the function. - a potential UAF when the lookup walks up the tree with new_ns != ns the new label refere ---truncated---

Quoted source text, attributed separately from HOL analysis.