{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72487 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72487 is a high-severity vulnerability in Linux, published on 15 Aug 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-72487 and fix it if it is affected.\n\nWhat it is: CVE-2026-72487 is a high-severity vulnerability in Linux, published on 15 Aug 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-72487 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-72487/ (Markdown: https://insights.sbomify.com/CVE-2026-72487/index.md)","id":"CVE-2026-72487","markdown":"https://insights.sbomify.com/CVE-2026-72487/index.md","name":"CVE-2026-72487","record":{"aliases":["BELL-CVE-2026-72487","DEBIAN-CVE-2026-72487","GHSA-8mf8-73cp-cjmq","UBUNTU-CVE-2026-72487"],"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":"none","summary":"A missing bounds check in the Linux kernel PCI ROM handling allows a local attacker to trigger a system crash via out-of-bounds memory access.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nPCI: Check ROM header and data structure addr before accessing\n\nWe meet a crash when running stress-ng on x86_64 machine:\n\n  BUG: unable to handle page fault for address: ffa0000007f40000\n  RIP: 0010:pci_get_rom_size+0x52/0x220\n  Call Trace:\n  \u003cTASK\u003e\n    pci_map_rom+0x80/0x130\n    pci_read_rom+0x4b/0xe0\n    kernfs_file_read_iter+0x96/0x180\n    vfs_read+0x1b1/0x300\n\nOur analysis reveals that the ROM space's start address is\n0xffa0000007f30000, and size is 0x10000. Because of broken ROM space,\nbefore calling readl(pds), the pds's value is 0xffa0000007f3ffff, which is\nalready pointed to the ROM space end, invoking readl() would read 4 bytes\ntherefore cause an out-of-bounds access and trigger a crash.  Fix this by\nadding image header and data structure checking.\n\nWe also found another crash on arm64 machine:\n\n  Unable to handle kernel paging request at virtual address ffff8000dd1393ff\n  Mem abort info:\n  ESR = 0x0000000096000021\n  EC = 0x25: DABT (current EL), IL = 32 bits\n  SET = 0, FnV = 0\n  EA = 0, S1PTW = 0\n  FSC = 0x21: alignment fault\n\nThe call trace is the same with x86_64, but the crash reason is that the\ndata structure addr is not aligned with 4, and arm64 machine report\n\"alignment fault\". Fix this by adding alignment checking.\n\n[bhelgaas: shorten function names, wrap comments]","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":"PCI: Check ROM header and data structure addr before accessing","id":"CVE-2026-72487","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"soundwire: fix bug in sdw_add_element_group_count found by syzkaller","id":"CVE-2026-72488"},"packages":[],"prev":{"headline":"mailbox: mtk-adsp: fix UAF during device teardown","id":"CVE-2026-72486"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["Linux"]},"summary":"A missing bounds check in the Linux kernel PCI ROM handling allows a local attacker to trigger a system crash via out-of-bounds memory access.","url":"https://insights.sbomify.com/CVE-2026-72487/"}