{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-23345 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-23345 is a medium-severity denial of service vulnerability in Linux kernel, published on 25 Mar 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-23345 and fix it if it is affected.\n\nWhat it is: CVE-2026-23345 is a medium-severity denial of service vulnerability in Linux kernel, published on 25 Mar 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-23345 in the wild and no public exploit code.\n\nAffected product: Linux kernel. 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-23345/ (Markdown: https://insights.sbomify.com/CVE-2026-23345/index.md)","id":"CVE-2026-23345","markdown":"https://insights.sbomify.com/CVE-2026-23345/index.md","name":"CVE-2026-23345","record":{"aliases":["BELL-CVE-2026-23345","DEBIAN-CVE-2026-23345","GHSA-67rr-wm48-f5vp","UBUNTU-CVE-2026-23345"],"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 kernel panic occurs when enabling GCS on ARM64 systems with LPA2 due to incorrect PTE shareability bits, causing a denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\narm64: gcs: Do not set PTE_SHARED on GCS mappings if FEAT_LPA2 is enabled\n\nWhen FEAT_LPA2 is enabled, bits 8-9 of the PTE replace the\nshareability attribute with bits 50-51 of the output address. The\n_PAGE_GCS{,_RO} definitions include the PTE_SHARED bits as 0b11 (this\nmatches the other _PAGE_* definitions) but using this macro directly\nleads to the following panic when enabling GCS on a system/model with\nLPA2:\n\n  Unable to handle kernel paging request at virtual address fffff1ffc32d8008\n  Mem abort info:\n    ESR = 0x0000000096000004\n    EC = 0x25: DABT (current EL), IL = 32 bits\n    SET = 0, FnV = 0\n    EA = 0, S1PTW = 0\n    FSC = 0x04: level 0 translation fault\n  Data abort info:\n    ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000\n    CM = 0, WnR = 0, TnD = 0, TagAccess = 0\n    GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0\n  swapper pgtable: 4k pages, 52-bit VAs, pgdp=0000000060f4d000\n  [fffff1ffc32d8008] pgd=100000006184b003, p4d=0000000000000000\n  Internal error: Oops: 0000000096000004 [#1]  SMP\n  CPU: 0 UID: 0 PID: 513 Comm: gcs_write_fault Tainted: G   M                7.0.0-rc1 #1 PREEMPT\n  Tainted: [M]=MACHINE_CHECK\n  Hardware name: QEMU QEMU Virtual Machine, BIOS 2025.02-8+deb13u1 11/08/2025\n  pstate: 03402005 (nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)\n  pc : zap_huge_pmd+0x168/0x468\n  lr : zap_huge_pmd+0x2c/0x468\n  sp : ffff800080beb660\n  x29: ffff800080beb660 x28: fff00000c2058180 x27: ffff800080beb898\n  x26: fff00000c2058180 x25: ffff800080beb820 x24: 00c800010b600f41\n  x23: ffffc1ffc30af1a8 x22: fff00000c2058180 x21: 0000ffff8dc00000\n  x20: fff00000c2bc6370 x19: ffff800080beb898 x18: ffff800080bebb60\n  x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000007\n  x14: 000000000000000a x13: 0000aaaacbbbffff x12: 0000000000000000\n  x11: 0000ffff8ddfffff x10: 00000000000001fe x9 : 0000ffff8ddfffff\n  x8 : 0000ffff8de00000 x7 : 0000ffff8da00000 x6 : fff00000c2bc6370\n  x5 : 0000ffff8da00000 x4 : 000000010b600000 x3 : ffffc1ffc0000000\n  x2 : fff00000c2058180 x1 : fffff1ffc32d8000 x0 : 000000c00010b600\n  Call trace:\n   zap_huge_pmd+0x168/0x468 (P)\n   unmap_page_range+0xd70/0x1560\n   unmap_single_vma+0x48/0x80\n   unmap_vmas+0x90/0x180\n   unmap_region+0x88/0xe4\n   vms_complete_munmap_vmas+0xf8/0x1e0\n   do_vmi_align_munmap+0x158/0x180\n   do_vmi_munmap+0xac/0x160\n   __vm_munmap+0xb0/0x138\n   vm_munmap+0x14/0x20\n   gcs_free+0x70/0x80\n   mm_release+0x1c/0xc8\n   exit_mm_release+0x28/0x38\n   do_exit+0x190/0x8ec\n   do_group_exit+0x34/0x90\n   get_signal+0x794/0x858\n   arch_do_signal_or_restart+0x11c/0x3e0\n   exit_to_user_mode_loop+0x10c/0x17c\n   el0_da+0x8c/0x9c\n   el0t_64_sync_handler+0xd0/0xf0\n   el0t_64_sync+0x198/0x19c\n  Code: aa1603e2 d34cfc00 cb813001 8b011861 (f9400420)\n\nSimilarly to how the kernel handles protection_map[], use a\ngcs_page_prot variable to store the protection bits and clear PTE_SHARED\nif LPA2 is enabled.\n\nAlso remove the unused PAGE_GCS{,_RO} macros.","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: gcs: Do not set PTE_SHARED on GCS mappings if FEAT_LPA2 is enabled","id":"CVE-2026-23345","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"arm64: io: Extract user memory type in ioremap_prot()","id":"CVE-2026-23346"},"packages":[],"prev":{"headline":"crypto: ccp - Fix use-after-free on error path","id":"CVE-2026-23344"},"products":["Linux"],"published":"2026-03-25","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A kernel panic occurs when enabling GCS on ARM64 systems with LPA2 due to incorrect PTE shareability bits, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2026-23345/"}