{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90212 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90212 is a memory corruption 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-90212 and fix it if it is affected.\n\nWhat it is: CVE-2026-90212 is a memory corruption 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-90212 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-90212/ (Markdown: https://insights.sbomify.com/CVE-2026-90212/index.md)","id":"CVE-2026-90212","markdown":"https://insights.sbomify.com/CVE-2026-90212/index.md","name":"CVE-2026-90212","record":{"aliases":["DEBIAN-CVE-2026-90212","GHSA-mvqq-j4gg-mmgx","UBUNTU-CVE-2026-90212"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"none","summary":"A race condition in Linux kernel EFI runtime services on ARM64 with software PAN enabled can cause kernel memory corruption and crashes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\narm64/efi: Avoid voluntary preemption with efi_mm installed\n\nGus reports a bad kernel memory access when using software PAN\n(CONFIG_ARM64_SW_TTBR0_PAN=y) on a machine with support for EFI runtime\nservices:\n\n  Unable to handle kernel access to user memory outside uaccess routines\n    at virtual address 00000000f322ff30\n  Mem abort info:\n    ESR = 0x0000000096000004\n    FSC = 0x04: level 0 translation fault\n  Internal error: Oops: 0000000096000004 [#1]  SMP\n  Workqueue: efi_rts_wq efi_call_rts\n  pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n  pc : efi_call_rts+0xd8/0x288\n  Call trace:\n   efi_call_rts+0xd8/0x288 (P)\n   process_one_work+0x178/0x4f8\n   worker_thread+0x194/0x328\n\nThis is because the fpsimd context management code called from\n__efi_fpsimd_begin() can preempt voluntarily, returning later to the EFI\ncode with an incorrect value for TTBR0_EL1 thanks to the deferred mm\nswitching used by the software PAN implementation.\n\nSince EFI runtime services cannot preempt voluntarily and because the\nfpsimd switching code does not rely on the TTBR0_EL1 mappings, simply\nreorder the fpsimd switch so that it occurs before we change the\npage-table.","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":"arm64/efi: Avoid voluntary preemption with efi_mm installed","id":"CVE-2026-90212","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"firewire: core: fix memory leak in error path of build_tree()","id":"CVE-2026-90213"},"packages":[],"prev":{"headline":"bpf, s390: Clear fetch destination on faulting arena atomic","id":"CVE-2026-90211"},"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 Linux kernel EFI runtime services on ARM64 with software PAN enabled can cause kernel memory corruption and crashes.","url":"https://insights.sbomify.com/CVE-2026-90212/"}