{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90179 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90179 is a denial of service vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-90179 and fix it if it is affected.\n\nWhat it is: CVE-2026-90179 is a denial of service vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-90179 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-90179/ (Markdown: https://insights.sbomify.com/CVE-2026-90179/index.md)","id":"CVE-2026-90179","markdown":"https://insights.sbomify.com/CVE-2026-90179/index.md","name":"CVE-2026-90179","record":{"aliases":["AZL-102846","BELL-CVE-2026-90179","DEBIAN-CVE-2026-90179","GHSA-wgph-2236-wgxv","UBUNTU-CVE-2026-90179"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can cause a kernel deadlock and hang processes by triggering a specific AppArmor complain-mode change_hat scenario.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix deadlock in complain-mode change_hat\n\nThe use of change_hat when in complain mode can cause a deadlock\nwhen the hat doesn't exist and a new learning profile is created\nfor the missing profile. This is because change_hat() has taken\nthe lock to search the hat list and creating the new learning\nprofile needs to take the lock to add it to the list.\n\nFrom the bug report:\n\nOriginally found in 7.0.0 in LTS ubuntu 26.04 with pam_apparmor + su\nin complain mode set to change hats.  Then verified in newest\navailable vanilla kernel I've compiled to see if still present:\n\n7.2-rc7 vanilla -\u003e affected\n\nchecked also some other kernels:\n6.18.44 vanilla -\u003e affected\n6.12.95 with debian patches -\u003e unaffected\n\nOn systems without bug (for example 6.12.95 debian) it just prints:\n\naa_change_hat rc=0\n\nOn systems with bug, the executable always hangs, prints nothing and\nbecomes unkillable.  (And once stuck this way, it will cause any\nfurther hat changes to also cause the changing process to get stuck)\n\nThen in syslog you can find hint about cause:\n\nkernel: INFO: task hat:3409 blocked for more than 483 seconds.\nkernel:       Not tainted 7.2.0-rc7 #1\nkernel: \"echo 0 \u003e /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\nkernel: task:hat             state:D stack:0     pid:3409  tgid:3409  ppid:2605   task_flags:0x400000 flags:0x00080800\nkernel: Call Trace:\nkernel:  \u003cTASK\u003e\nkernel:  __schedule+0x48f/0xfe0\nkernel:  schedule+0x27/0xa0\nkernel:  schedule_preempt_disabled+0x15/0x30\nkernel:  __mutex_lock.constprop.0+0x569/0xa10\nkernel:  aa_new_learning_profile+0x15f/0x210\nkernel:  build_change_hat+0x19f/0x3b0\nkernel:  change_hat.isra.0+0x5dd/0xd60\nkernel:  aa_change_hat+0x2f3/0x710\nkernel:  aa_setprocattr_changehat+0x121/0x1f0\nkernel:  do_setattr+0x28c/0x340\nkernel:  apparmor_setselfattr+0x20/0x50\nkernel:  security_setselfattr+0xf6/0x110\nkernel:  __x64_sys_lsm_set_self_attr+0x53/0x90\nkernel:  do_syscall_64+0xdd/0x5e0\nkernel:  ? __mod_memcg_lruvec_state+0xfd/0x260\nkernel:  ? lruvec_stat_mod_folio+0x8d/0xd0\nkernel:  ? __folio_mod_stat+0x2d/0x90\nkernel:  ? map_anon_folio_pte_nopf+0xd1/0x1f0\nkernel:  ? do_anonymous_page+0x184/0xa10\nkernel:  ? __handle_mm_fault+0x805/0x870\nkernel:  ? count_memcg_events+0xef/0x230\nkernel:  ? handle_mm_fault+0x1f0/0x2f0\nkernel:  ? do_user_addr_fault+0x2bb/0x7b0\nkernel:  ? do_syscall_64+0x94/0x5e0\nkernel:  ? exc_page_fault+0x75/0x160\nkernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e\nkernel: RIP: 0033:0x7f815e134c8d\nkernel: RSP: 002b:00007fff6df94ea8 EFLAGS: 00000246 ORIG_RAX: 00000000000001cc\nkernel: RAX: ffffffffffffffda RBX: 0000556d8c81d040 RCX: 00007f815e134c8d\nkernel: RDX: 0000000000000046 RSI: 0000556d8c81d040 RDI: 0000000000000064\nkernel: RBP: 00007fff6df94ef0 R08: 00007f815e212ac8 R09: 000000000000000c\nkernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000556d8c81d010\nkernel: R13: 0000000000000026 R14: 0000000000000046 R15: 0000000000000064\nkernel:  \u003c/TASK\u003e\nkernel: INFO: task hat:3409 is blocked on a mutex likely owned by task hat:3409.\n\nTo fix the issue, lift the locking out of the core of\naa_new_learning_profile(), introduce a wrapper function that takes the\nlock where needed, and have build_change_hat() call the core function\nthat no longer takes the lock.\n\nIn addition fix 4 other issues introduced by commit\n32e92764d6f8d (\"apparmor: grab ns lock and refresh when looking up changehat child profiles\")\n- aa_get_profile_rcu() was replaced-by: aa_get_profile without the\n  accompanying rcu_dereference_protected()\n- an extra aa_get_label(label) was introduced at the start of\n  change_hat() without an accompanying aa_put_label() causing a\n  reference count leak.\n- a reference count leak was introduced in the label_is_stale(label)\n  case, where the newest profile would be leaked instead of the\n  label passed to the function.\n- a potential UAF when the lookup walks up the tree with new_ns != ns\n  the new label refere\n---truncated---","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"apparmor: fix deadlock in complain-mode change_hat","id":"CVE-2026-90179","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"block: mtip32xx: synchronize ioctls with device removal","id":"CVE-2026-90180"},"packages":[],"prev":{"headline":"hwmon: (coretemp) Fix core_data leak on CPUs without PTS","id":"CVE-2026-90178"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"A local attacker can cause a kernel deadlock and hang processes by triggering a specific AppArmor complain-mode change_hat scenario.","url":"https://insights.sbomify.com/CVE-2026-90179/"}