{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-31600 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-31600 is a high-severity vulnerability in Linux kernel, published on 24 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-31600 and fix it if it is affected.\n\nWhat it is: CVE-2026-31600 is a high-severity vulnerability in Linux kernel, published on 24 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-31600 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-31600/ (Markdown: https://insights.sbomify.com/CVE-2026-31600/index.md)","id":"CVE-2026-31600","markdown":"https://insights.sbomify.com/CVE-2026-31600/index.md","name":"CVE-2026-31600","record":{"aliases":["AZL-83759","BELL-CVE-2026-31600","DEBIAN-CVE-2026-31600","GHSA-6447-4w47-gh9g","ROOT-OS-DEBIAN-11-CVE-2026-31600","ROOT-OS-DEBIAN-12-CVE-2026-31600","ROOT-OS-DEBIAN-13-CVE-2026-31600","UBUNTU-CVE-2026-31600"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A null pointer dereference in the Linux kernel arm64 memory management code can cause a kernel panic during boot on specific systems.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\narm64: mm: Handle invalid large leaf mappings correctly\n\nIt has been possible for a long time to mark ptes in the linear map as\ninvalid. This is done for secretmem, kfence, realm dma memory un/share,\nand others, by simply clearing the PTE_VALID bit. But until commit\na166563e7ec37 (\"arm64: mm: support large block mapping when\nrodata=full\") large leaf mappings were never made invalid in this way.\n\nIt turns out various parts of the code base are not equipped to handle\ninvalid large leaf mappings (in the way they are currently encoded) and\nI've observed a kernel panic while booting a realm guest on a\nBBML2_NOABORT system as a result:\n\n[   15.432706] software IO TLB: Memory encryption is active and system is using DMA bounce buffers\n[   15.476896] Unable to handle kernel paging request at virtual address ffff000019600000\n[   15.513762] Mem abort info:\n[   15.527245]   ESR = 0x0000000096000046\n[   15.548553]   EC = 0x25: DABT (current EL), IL = 32 bits\n[   15.572146]   SET = 0, FnV = 0\n[   15.592141]   EA = 0, S1PTW = 0\n[   15.612694]   FSC = 0x06: level 2 translation fault\n[   15.640644] Data abort info:\n[   15.661983]   ISV = 0, ISS = 0x00000046, ISS2 = 0x00000000\n[   15.694875]   CM = 0, WnR = 1, TnD = 0, TagAccess = 0\n[   15.723740]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0\n[   15.755776] swapper pgtable: 4k pages, 48-bit VAs, pgdp=0000000081f3f000\n[   15.800410] [ffff000019600000] pgd=0000000000000000, p4d=180000009ffff403, pud=180000009fffe403, pmd=00e8000199600704\n[   15.855046] Internal error: Oops: 0000000096000046 [#1]  SMP\n[   15.886394] Modules linked in:\n[   15.900029] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 7.0.0-rc4-dirty #4 PREEMPT\n[   15.935258] Hardware name: linux,dummy-virt (DT)\n[   15.955612] pstate: 21400005 (nzCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--)\n[   15.986009] pc : __pi_memcpy_generic+0x128/0x22c\n[   16.006163] lr : swiotlb_bounce+0xf4/0x158\n[   16.024145] sp : ffff80008000b8f0\n[   16.038896] x29: ffff80008000b8f0 x28: 0000000000000000 x27: 0000000000000000\n[   16.069953] x26: ffffb3976d261ba8 x25: 0000000000000000 x24: ffff000019600000\n[   16.100876] x23: 0000000000000001 x22: ffff0000043430d0 x21: 0000000000007ff0\n[   16.131946] x20: 0000000084570010 x19: 0000000000000000 x18: ffff00001ffe3fcc\n[   16.163073] x17: 0000000000000000 x16: 00000000003fffff x15: 646e612065766974\n[   16.194131] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000\n[   16.225059] x11: 0000000000000000 x10: 0000000000000010 x9 : 0000000000000018\n[   16.256113] x8 : 0000000000000018 x7 : 0000000000000000 x6 : 0000000000000000\n[   16.287203] x5 : ffff000019607ff0 x4 : ffff000004578000 x3 : ffff000019600000\n[   16.318145] x2 : 0000000000007ff0 x1 : ffff000004570010 x0 : ffff000019600000\n[   16.349071] Call trace:\n[   16.360143]  __pi_memcpy_generic+0x128/0x22c (P)\n[   16.380310]  swiotlb_tbl_map_single+0x154/0x2b4\n[   16.400282]  swiotlb_map+0x5c/0x228\n[   16.415984]  dma_map_phys+0x244/0x2b8\n[   16.432199]  dma_map_page_attrs+0x44/0x58\n[   16.449782]  virtqueue_map_page_attrs+0x38/0x44\n[   16.469596]  virtqueue_map_single_attrs+0xc0/0x130\n[   16.490509]  virtnet_rq_alloc.isra.0+0xa4/0x1fc\n[   16.510355]  try_fill_recv+0x2a4/0x584\n[   16.526989]  virtnet_open+0xd4/0x238\n[   16.542775]  __dev_open+0x110/0x24c\n[   16.558280]  __dev_change_flags+0x194/0x20c\n[   16.576879]  netif_change_flags+0x24/0x6c\n[   16.594489]  dev_change_flags+0x48/0x7c\n[   16.611462]  ip_auto_config+0x258/0x1114\n[   16.628727]  do_one_initcall+0x80/0x1c8\n[   16.645590]  kernel_init_freeable+0x208/0x2f0\n[   16.664917]  kernel_init+0x24/0x1e0\n[   16.680295]  ret_from_fork+0x10/0x20\n[   16.696369] Code: 927cec03 cb0e0021 8b0e0042 a9411c26 (a900340c)\n[   16.723106] ---[ end trace 0000000000000000 ]---\n[   16.752866] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b\n[   16.792556] Kernel Offset: 0x3396ea200000 from 0xffff8000800000\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":"arm64: mm: Handle invalid large leaf mappings correctly","id":"CVE-2026-31600","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"vfio/xe: Reorganize the init to decouple migration from reset","id":"CVE-2026-31601"},"packages":[],"prev":{"headline":"media: vidtv: fix NULL pointer dereference in vidtv_channel_pmt_match_sections","id":"CVE-2026-31599"},"products":["Linux"],"published":"2026-04-24","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A null pointer dereference in the Linux kernel arm64 memory management code can cause a kernel panic during boot on specific systems.","url":"https://insights.sbomify.com/CVE-2026-31600/"}