{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89722 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89722 is a memory corruption vulnerability in Linux, published on 11 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-89722 and fix it if it is affected.\n\nWhat it is: CVE-2026-89722 is a memory corruption vulnerability in Linux, published on 11 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-89722 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-89722/ (Markdown: https://insights.sbomify.com/CVE-2026-89722/index.md)","id":"CVE-2026-89722","markdown":"https://insights.sbomify.com/CVE-2026-89722/index.md","name":"CVE-2026-89722","record":{"aliases":["AZL-100895","BELL-CVE-2026-89722","DEBIAN-CVE-2026-89722","GHSA-chvm-2qwm-x2xc","UBUNTU-CVE-2026-89722"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"high_privilege","summary":"A local root user can trigger an out-of-bounds read in the Linux kernel PCI sysfs interface, potentially leaking memory or causing a 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\nPCI/sysfs: Fix out-of-bounds read in pci_write_legacy_io()\n\npci_write_legacy_io() loads 4 bytes from the kernfs write buffer\nregardless of how many bytes userspace wrote:\n\n  if (count != 1 \u0026\u0026 count != 2 \u0026\u0026 count != 4)\n          return -EINVAL;\n\n  return pci_legacy_write(bus, off, *(u32 *)buf, count);\n\nkernfs_fop_write_iter() allocates the buffer with kmalloc(len + 1),\nso a 1-byte write to the legacy_io sysfs file allocates 2 bytes and\nthe unconditional u32 load reads up to 2 bytes past the end of the\nallocation, which KASAN reports as a slab-out-of-bounds read.\nSimilarly, a 2-byte write overreads by 1 byte.\n\nThus, read only the number of bytes requested using get_unaligned_le16()\nand get_unaligned_le32() for the 2 and 4 byte cases, interpreting the\nbuffer as little-endian to match the byte ordering of PCI I/O port\nspace.\n\nThe PowerPC implementation previously compensated for the generic\ncode's native-endian 32-bit load by shifting the value into place\nfor the 1 and 2 byte cases.  The shifts were only correct on\nbig-endian kernels.\n\nOn little-endian PowerPC (POWER8 and later), they extracted the wrong\nbytes, so a 1-byte write wrote an out-of-bounds byte instead of the\nrequested value.  On big-endian, the native load also caused out_le16()\nand out_le32() to reverse the user's bytes on the wire for 2 and 4 byte\nwrites.  The little-endian helpers resolve both issues, so the shifts\nare removed.\n\nNo changes are needed for the Alpha platform.\n\nThe legacy_io file is root-only and exists only on Alpha and PowerPC,\nthe two architectures that define HAVE_PCI_LEGACY.","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/sysfs: Fix out-of-bounds read in pci_write_legacy_io()","id":"CVE-2026-89722","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"nilfs2: fix slab-out-of-bounds in nilfs_direct_propagate after truncation","id":"CVE-2026-89723"},"packages":[],"prev":{"headline":"phy: rockchip-samsung-dcphy: fix out-of-range max_register","id":"CVE-2026-89721"},"products":["Linux"],"published":"2026-09-11","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 root user can trigger an out-of-bounds read in the Linux kernel PCI sysfs interface, potentially leaking memory or causing a crash.","url":"https://insights.sbomify.com/CVE-2026-89722/"}