{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97947 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97947 is a 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-97947 and fix it if it is affected.\n\nWhat it is: CVE-2026-97947 is a 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-97947 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-97947/ (Markdown: https://insights.sbomify.com/CVE-2026-97947/index.md)","id":"CVE-2026-97947","markdown":"https://insights.sbomify.com/CVE-2026-97947/index.md","name":"CVE-2026-97947","record":{"aliases":["BELL-CVE-2026-97947","DEBIAN-CVE-2026-97947","GHSA-xj5r-4m42-gc82","UBUNTU-CVE-2026-97947"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can trigger a NULL pointer dereference in the Linux kernel's AMD node driver, causing a system crash.","user_interaction":"not_required","vuln_class":"null_dereference"},"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/amd_node: Fix potential NULL pointer dereference\n\namd_smn_read/write() are exported functions around __amd_smn_rw(), so\nthey are always available even if amd_smn_init() fails. In that case,\n'amd_roots' is NULL and __amd_smn_rw() will access uninitialized memory.\n\nThen, commit:\n\n  83518453074d (\"x86/amd_node: Add SMN offsets to exclusive region access\")\n\nadded the 'smn_exclusive' flag, which indicated the calls to\npci_request_config_region_exclusive() succeeded, to prevent\nconcurrent userspace access.\n\nCommit:\n\n  0a4b61d9c2e4 (\"x86/amd_node: Fix AMD root device caching\")\n\nre-ordered initialization so pci_request_config_region_exclusive() is\ncalled earlier and a failure exits amd_smn_init() before allocating\n'amd_roots'. The setting of 'smn_exclusive' moved to the end of\namd_smn_init(), after 'amd_roots' is allocated. It became redundant\nand can be removed.\n\nReplace 'smn_exclusive' with directly checking 'amd_roots', to fix a\npotential NULL pointer dereference and to simplify the logic.\n\n  [ bp: Reorg commit message, touchup comment. ]\n  [ mingo: Rebase \u0026 further touchups. ]","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/amd_node: Fix potential NULL pointer dereference","id":"CVE-2026-97947","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"powerpc/eeh: Fix recursive locking on devices without EEH sensitive driver","id":"CVE-2026-97948"},"packages":[],"prev":{"headline":"x86/amd_node: Fix PCI device reference counting in amd_smn_init()","id":"CVE-2026-97946"},"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 local attacker can trigger a NULL pointer dereference in the Linux kernel's AMD node driver, causing a system crash.","url":"https://insights.sbomify.com/CVE-2026-97947/"}