{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98640 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98640 is a memory corruption vulnerability in Linux, published on 18 Oct 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-98640 and fix it if it is affected.\n\nWhat it is: CVE-2026-98640 is a memory corruption vulnerability in Linux, published on 18 Oct 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-98640 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-98640/ (Markdown: https://insights.sbomify.com/CVE-2026-98640/index.md)","id":"CVE-2026-98640","markdown":"https://insights.sbomify.com/CVE-2026-98640/index.md","name":"CVE-2026-98640","record":{"aliases":["AZL-109416","BELL-CVE-2026-98640","DEBIAN-CVE-2026-98640","GHSA-5m32-w674-2xq4","UBUNTU-CVE-2026-98640"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A missing size check in the AMD SFH HID driver allows out-of-bounds memory access, causing a kernel page fault and system crash.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\nHID: amd_sfh: Validate PCI BAR size before mapping\n\nThe amd_sfh driver maps PCI BAR 2 using pcim_iomap_regions() and\nsubsequently accesses MMIO registers at offsets up to 0x10958 (e.g.,\nAMD_P2C_MSG3 at 0x1068C). However, the driver never validates that the BAR\nsize is large enough to cover these accesses. If the driver is bound to a\ndevice with a smaller BAR 2, this leads to an out-of-bounds memory access\nand a page fault during the probe function.\n\nFor example, a page fault can occur when reading from privdata-\u003emmio +\nAMD_P2C_MSG3 in mp2_select_ops():\n\n  BUG: unable to handle page fault for address: ffffc9000390368c\n  PGD 100000067 P4D 100000067 PUD 1012c1067 PMD 105b64067 PTE 0\n  Oops: Oops: 0000 [#1] SMP KASAN NOPTI\n  RIP: 0010:readl arch/x86/include/asm/io.h:59 [inline]\n  RIP: 0010:mp2_select_ops drivers/hid/amd-sfh-hid/amd_sfh_pcie.c:282\n  [inline]\n  RIP: 0010:amd_mp2_pci_probe+0x337/0x5f0\n  drivers/hid/amd-sfh-hid/amd_sfh_pcie.c:487\n  Call Trace:\n   \u003cTASK\u003e\n   local_pci_probe drivers/pci/pci-driver.c:332 [inline]\n   pci_call_probe drivers/pci/pci-driver.c:394 [inline]\n   __pci_device_probe drivers/pci/pci-driver.c:455 [inline]\n   pci_device_probe+0x431/0xc90 drivers/pci/pci-driver.c:489\n\nFix this by verifying that the length of BAR 2 is at least 128KB before\nattempting to map it. Since the maximum accessed offset is 0x10958, and PCI\nBAR sizes are powers of 2, any legitimate hardware will have a BAR size of\nat least 128KB.","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":"HID: amd_sfh: Validate PCI BAR size before mapping","id":"CVE-2026-98640","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"bpf, arm64: set up the frame pointer for the exception callback","id":"CVE-2026-98641"},"packages":[],"prev":{"headline":"KVM: riscv: Fix NACL hfence entry update order","id":"CVE-2026-98639"},"products":["Linux"],"published":"2026-10-18","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 missing size check in the AMD SFH HID driver allows out-of-bounds memory access, causing a kernel page fault and system crash.","url":"https://insights.sbomify.com/CVE-2026-98640/"}