{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97533 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97533 is an use after free vulnerability in Linux, published on 25 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-97533 and fix it if it is affected.\n\nWhat it is: CVE-2026-97533 is an use after free vulnerability in Linux, published on 25 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-97533 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-97533/ (Markdown: https://insights.sbomify.com/CVE-2026-97533/index.md)","id":"CVE-2026-97533","markdown":"https://insights.sbomify.com/CVE-2026-97533/index.md","name":"CVE-2026-97533","record":{"aliases":["BELL-CVE-2026-97533","DEBIAN-CVE-2026-97533","GHSA-4g49-6xf9-67qq","UBUNTU-CVE-2026-97533"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"high_privilege","summary":"A race condition in the Linux kernel x86/mm/pat subsystem allows a use-after-free, potentially enabling local attackers to execute code or escalate privileges.","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\nx86/mm/pat: Acquire init_mm read lock on attribute changes to avoid UAF\n\nA previous commit protected against races between ptdump and CPA collapse,\nhowever one still exists between attribute changes and collapse as reported\nby Denis V. Lunev (linked).\n\nWhen an attribute change arises, a lockless page table walker obtains a PTE\nentry, which is later written to via set_pte_atomic():\n\n  ...\n  -\u003e change_page_attr_set_clr()\n  -\u003e __change_page_attr_set_clr()\n  -\u003e __change_page_attr()\n\t-\u003e _lookup_address_cpa()\n\t-\u003e lookup_address_in_pgd_attr()\n\t-\u003e [ lockless page table walker ]\n  -\u003e set_pte_atomic()\n\nThere is nothing preventing a concurrent CPA collapse which can free the\nPTE that was retrieved here, resulting in a use-after-free.\n\nWith the mmap write lock taken on init_mm over CPA collapse, resolve this\nrace by acquiring an mmap read lock on init_mm over\n__change_page_attr_set_clr().\n\nThis locks across the whole operation over which the walk and the PTE\nentry write occurs, solving the race.\n\nIt is safe to do this here, as no spinlocks are held upon entry to\n__change_page_attr_set_clr().\n\nHowever, the lock must not be held over an allocation, as allocation can\ntrigger reclaim and shrinkers may call into CPA recursively, making\ndeadlocks possible (init_mm -\u003e ... -\u003e fs_reclaim -\u003e init_mm).\n\nA page table is allocated when a huge page needs to be split:\n\n  -\u003e change_page_attr_set_clr()\n  -\u003e __change_page_attr_set_clr()\n  -\u003e __change_page_attr()\n  -\u003e split_large_page()\n  [ pagetable_alloc() ]\n  -\u003e __split_large_page()\n\nAvoid deadlocks by dropping the mmap lock across pagetable_alloc() in\nsplit_large_page() and track whether this is needed by adding a new\n'init_mm_read_locked' flag to struct cpa_data.\n\nThis is safe as __split_large_page() (called with locks re-established)\nrevalidates that the page table entry is the same as it was prior to the\nlocks being dropped and __change_page_attr() repeats the entire page table\nwalk whenever a split occurs, so concurrent split and collapse are\naccounted for.\n\nConcurrent ptdump is also safe as the lock is only dropped over page table\nallocation during which time the page table has not yet been modified.\n\nThe CPA_COLLAPSE flag is only set by set_memory_rox(), which exclusively\noperates upon vmalloc ranges, and on x86 only within the module mapping\nspace.\n\nThis is important, because some callers directly invoke\n__change_page_attr_set_clr(), bypassing this lock. However, none of these\noperate within the module mapping space.\n\n  * cpa_process_alias() - a recursive helper called by\n    __change_page_attr_set_clr().\n  * __set_memory_enc_pgtable() - operates on the direct mapping and (via\n    __vmbus_establish_gpadl()) the vmalloc mapping space.\n  * __set_pages_[n]p() - called by set_direct_map_[invalid, default,\n    valid]_noflush(), __kernel_map_pages() - operates on the direct map.\n  * kernel_[un]map_pages_in_pgd() - operates on EFI ranges.\n\nThis work is based upon Denis V. Lunev's excellent analysis of the bug\nwith gratitude.\n\n[ dhansen: move to imperative voice in changelog ]","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":"x86/mm/pat: Acquire init_mm read lock on attribute changes to avoid UAF","id":"CVE-2026-97533","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"f2fs: accurately adjust free_sections during free_segment_range","id":"CVE-2026-97534"},"packages":[],"prev":{"headline":"scsi: qla2xxx: Null out freed pointers in qla2x00_mem_alloc() error path","id":"CVE-2026-97532"},"products":["Linux"],"published":"2026-09-25","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 x86/mm/pat subsystem allows a use-after-free, potentially enabling local attackers to execute code or escalate privileges.","url":"https://insights.sbomify.com/CVE-2026-97533/"}