{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90303 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90303 is an use after free 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-90303 and fix it if it is affected.\n\nWhat it is: CVE-2026-90303 is an use after free 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-90303 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-90303/ (Markdown: https://insights.sbomify.com/CVE-2026-90303/index.md)","id":"CVE-2026-90303","markdown":"https://insights.sbomify.com/CVE-2026-90303/index.md","name":"CVE-2026-90303","record":{"aliases":["AZL-101873","BELL-CVE-2026-90303","DEBIAN-CVE-2026-90303","GHSA-3rvr-4rpw-5w37","UBUNTU-CVE-2026-90303"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"none","summary":"A race condition in the Linux kernel ARM memory management can cause a use-after-free and kernel panic when debug user faults are enabled.","user_interaction":"not_required","vuln_class":"use_after_free"},"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\nARM: 9485/1: mm: acquire mmap write lock around show_pte() for user faults\n\nWhen CONFIG_DEBUG_USER=y, and cmdline \"user_debug=31\" is set,\na user fault may trigger show_pte() without any lock.\nIf another thread in the same process concurrently calls munmap(),\nthe page table pages may be freed while show_pte() is still traversing\nthem, causing a use-after-free in show_pte().\n\nIf CONFIG_ARM_LPAE=y, this may cause a kernel panic if the pages table\nof PMD are freed when show_pte() is running.\n\nAcquire mmap_write_lock() around show_pte() for user faults to fix the\ncontention.\n\nFor user faults, additionally restrict that show_pte() is called only\nwhen the addr is a user-space address (addr \u003c TASK_SIZE). This is because\nthe lock of tsk-\u003emm only protects the virtual memory of user address space,\nfurthermore, dumping the page tables of a kernel-space address for user\nfaults is unnecessary and may have security implications.\n\nKeep everything unchanged for kernel faults, because the kernel is\nalready in the \"oops\" state, acquiring a lock may risk a deadlock.","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":"ARM: 9485/1: mm: acquire mmap write lock around show_pte() for user faults","id":"CVE-2026-90303","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"ARM: 9484/1: enable interrupts when unhandled user faults are triggered","id":"CVE-2026-90304"},"packages":[],"prev":{"headline":"ocfs2: synchronize heartbeat callbacks with o2net teardown","id":"CVE-2026-90302"},"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-19","vendors":["Linux"]},"summary":"A race condition in the Linux kernel ARM memory management can cause a use-after-free and kernel panic when debug user faults are enabled.","url":"https://insights.sbomify.com/CVE-2026-90303/"}